I reckon that the handle $@ in a shell script is an array of all arguments given to the script. Is this true? I ask because I normally use search engines to gather information, but I can’t google for $@ and I have grown too accustomed to easily getting served everything.
You could use printf instead: printf has more consistent behavior than echo. The behavior of echo varies greatly between different versions.
edit: I prefer seq over the other methods because I can actually remember it 😉
To check if a directory exists in a shell script, you can use the following: Or to check if a directory doesn’t exist: However, as Jon Ericson points out, subsequent commands may not work as intended if you do not take into account that a symbolic link to a directory will also pass this check. E.g. running … Read more
When all else fails in Cygwin… Try running the dos2unix command on the file in question. It might help when you see error messages like this: -bash: ‘\r’: command not found Windows style newline characters can cause issues in Cygwin. The dos2unix command modifies newline characters so they are Unix / Cygwin compatible. CAUTION: the dos2unix command modifies files in place, … Read more
You can use it like this: Also works for multi-line array declaration
What you have should work, unless ${STATUS} is empty. It would probably be better to do: or It’s hard to say, since you haven’t shown us exactly what is going wrong with your script. Personal opinion: never use [[. It suppresses important error messages and is not portable to different shells.
The characters ‘<‘, and ‘>’, are to indicate a place-holder, you should remove them to read:
I have seen this issue when creating scripts in Windows env and then porting over to run on a Unix environment. Try running dos2unix on the script: http://dos2unix.sourceforge.net/ Or just rewrite the script in your Unix env using vi and test. Unix uses different line endings so can’t read the file you created on Windows. Hence it is seeing … Read more
When all else fails in Cygwin… Try running the dos2unix command on the file in question. It might help when you see error messages like this: -bash: ‘\r’: command not found Windows style newline characters can cause issues in Cygwin. The dos2unix command modifies newline characters so they are Unix / Cygwin compatible. CAUTION: the dos2unix command modifies files in place, … Read more