2 ms·
I get my "best practices" from here: https://tldp.org/LDP/abs/html/index.html https://tldp.org/LDP/abs/html/index.html I think this site is amazing, and it mus
by tuvi13 4y ago
I get my "best practices" from here: https://tldp.org/LDP/abs/html/index.html https://tldp.org/LDP/abs/html/index.html
I think this site is amazing, and it must be older than at least two decades.
- ndsipa_pomu 4y agoI used to refer to that all the time, but it doesn't have newer bashisms (shell != bash). A better resource is https://mywiki.wooledge.org/BashGuide https://mywiki.wooledge.org/BashGuide Also, a preliminary read of https://mywiki.wooledge.org/BashPitfalls https://mywiki.wooledge.org/BashPitfalls is advised. Using shellcheck as a bash/shell linter is the ultimate. When you get a new warning, you can look up the code and learn why it's complaining.