pottmi

3 ms·

1.
by pottmi 1y ago
I switched to zsh so I have not been paying attention to bash so I don't have a top three things to add. I just add things as I stumble on them. Thanks for the tip on reference variables. definitely better than eval. i will add that
2.
by pottmi 1y ago
It is what I advise people that want to make a presentation to give to their local LUG. Do the presentation on something "evergreen" that will last a long time. File permission, regular expression, /proc file system, ...
3.
by pottmi 1y ago
Yeah, despite having created that presentation and having given it 50 times if I were to do another IBM JCL to shell conversion I would convert to zsh.
4.
by pottmi 1y ago
You will like the final version of the traperr ERR function. It looks to create a "stack trace" type dump of where you are in the script when it fails. See it here: https://github.com/pottmi/stringent.sh
5.
by pottmi 1y ago
Here is a https link to the presentation and the stringent.sh library: https://github.com/pottmi/stringent.sh
6.
by pottmi 1y ago
It is not how to code in bash, it is how to avoid the bash pitfalls.
7.
by pottmi 1y ago
I contacted the guys that run the site and asked them to add https. I will throw the pdf on my gitlab account that has the stringent.sh script. https://github.com/pottmi/stringent.sh
8.
by pottmi 1y ago
It was done in keynote on a mac in 2006. I still maintain the 2025 version in keynote on a mac.
9.
by pottmi 1y ago
Are you bashing bash?
10.
by pottmi 1y ago
I am the author of this presentation. Feel free to ask me questions and send me corrections to the pdf and youtube video. Here is are the slides: http://uniforumchicago.org/slides/bash_2025-03-25.pdf Here is the record