this post was submitted on 08 Jul 2023
8 points (100.0% liked)

Shell Scripting

1346 readers
1 users here now

From Ash, Bash and Csh to Xonsh, Ysh and Zsh; all shell languages are welcome here!

Rules:
  1. Follow Lemmy rules!
  2. Posts must relate to shell scripting. (See bottom of sidebar for more information.)
  3. Only make helpful replies to questions. This is not the place for low effort joke answers.
  4. No discussion about piracy or hacking.
  5. If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
  6. These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:


In general, if your submission text is primarily shell code, then it is welcome here!

founded 1 year ago
MODERATORS
 

i'm pretty new to the shell scripting world and not sure, if i should give my scripts a .sh or .bash extension.

not sure what the pros and cons are.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 7 points 1 year ago* (last edited 1 year ago) (1 children)

If we're talking specifically about executable scripts, here is #bash's (libera.chat) factoid on the matter:

Don't use extensions for your scripts. Scripts define new commands that you can run, and commands are generally not given extensions. Do you run ls.elf? Also: bash scripts are not sh scripts (so don't use .sh) and the extension will only cause dependencies headaches if the script gets rewritten in another language. See http://www.talisman.org/~erlkonig/documents/commandname-extensions-considered-harmful

It's for these reasons that I keep my executable scripts named without extensions (e.g. install).

I sometimes have non-executable scripts: they're chmod -x, they don't have a shebang, and they're explicitly made for source-ing (e.g. library functions). For these, I give them an extension depending on what shell I wrote them for (and thus, what shell you need to use to source them), e.g. library.bash or library.zsh.

[โ€“] [email protected] 1 points 1 year ago

I do the same, but I include shebangs anyway out of habit.