(12-11-2020, 02:57 PM)stratex Wrote: So we are not using Bourne shell, or something strictly POSIX compliant, we are using BASH, I thought, why not using .bash for bash scripts, and .sh for posix compliant ones.

Executables are the one place where I usually don’t use a file name extension. It happens surprisingly often that I re-implement a script in another scripting language or in C. When that happens, I don’t want to update all other programs/scripts to now use `make-html-index.py` instead of `make-html-index.sh` and then 3 months later just `make-html-index`, because I finally went for C (or Go or Rust or …).

All other files usually get an extension – if I intend to keep them around. I want a simple `ls` to indicate which kind of file it probably is. Then of course there is stuff like `README`, where I don’t use an extension. Now that I think about it, it’s much more inconsistent than I was aware of.