inadvertently
when replacing with a Bash scriptfoo="bar"
I wrote =
with spaces before and after oo
, but the foo
was not replaced and the error did not occur.
Using the same description on an interactive bash shell
bash:foo:command not found
It's an error, but why don't you throw up the error in the script?
bash
I wrote the variable name foo
in the question.
In an environment where there were no errors, the variable name used the name basename
as the command.
The command not found
error did not appear, and it seemed to be treated as a variable with a blank string after the substitute line.
I have posted an answer to close the question, although it contains information that was not included in the question.
I don't need any space when I replace it with bash.Run line by line, so if you write foo="bar", you execute the foot command, where = and "bar" are arguments.Without the foo command, the command not found error appears.
It looks like ls-la./.If ls is changed to sdfsdfsdf, sdfsdf-la. / Same, command not found error should appear.
574 Who developed the "avformat-59.dll" that comes with FFmpeg?
573 rails db:create error: Could not find mysql2-0.5.4 in any of the sources
618 Uncaught (inpromise) Error on Electron: An object could not be cloned
915 When building Fast API+Uvicorn environment with PyInstaller, console=False results in an error
© 2024 OneMinuteCode. All rights reserved.