Thanks! I thought that only variables without curly braces should be wrapped in quotes. I'll update the article later to include this, thanks for the advice.
I agree on using bash for #! as most of my scripts, for now, are just for mine own usage, and I guess that all my friends at least have the bash shell on theirs PC-s if not actively using it.
Another thing that I've noticed is that with #! /bin/bash, if the user doesn't have it installed, the error will be something like: cannot find command: /bin/bash and the user can install it in mere minutes instead of getting a cryptic message I got because of using #! /bin/sh when I've experimented with shell functions and spent another 15 minutes trying to resolve the issue.
Shellscripts that will be used in production env, it may be a bit better to use #! /bin/sh but that can fail too, so there is no right answer I guess.
If you're using #! /bin/sh you have to be POSIX compliant, otherwise you might destroy something along the way, because you cannot know what shell you are running on.
If you are relying on bash built-in, obviously you have to specify that, otherwise you might again destroy stuff.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks! I thought that only variables without curly braces should be wrapped in quotes. I'll update the article later to include this, thanks for the advice.
I agree on using bash for
#!as most of my scripts, for now, are just for mine own usage, and I guess that all my friends at least have the bash shell on theirs PC-s if not actively using it.Another thing that I've noticed is that with
#! /bin/bash, if the user doesn't have it installed, the error will be something like:cannot find command: /bin/bashand the user can install it in mere minutes instead of getting a cryptic message I got because of using#! /bin/shwhen I've experimented with shell functions and spent another 15 minutes trying to resolve the issue.Shellscripts that will be used in production env, it may be a bit better to use
#! /bin/shbut that can fail too, so there is no right answer I guess.If you're using
#! /bin/shyou have to be POSIX compliant, otherwise you might destroy something along the way, because you cannot know what shell you are running on.If you are relying on bash built-in, obviously you have to specify that, otherwise you might again destroy stuff.