Well, that won’t work on openbsd (and probably freebsd), because non-default.stuff lands in /usr/local/bin.

For Linux you should be fine though.

Uhm, yes. I noted exactly that as well.

Also bash is not always at /bin/bash :-)

Let me just drop my materials for a talk i’ve given about basically this topic: https://codeberg.org/flart/you_suck_at_shell_scripting/src/branch/main/you_suck.md

Mainly because: The linked article is all nice and dandy, but it completely ignores the topic of double brackets and why they’re nice.

And also, and this is my very strong opinion: if you end up thinking about exception handling (like the mentioned traps) in shell scripts, you should stop immediately and switch to a proper programming language.

Shell scripts are great, i love them. But they have an area they’re good for and a lot of areas where they aren’t.

Dumdum bullets and shoot to kill.

Oh it will definitely tell you something. It will be complete bullshit, but it’s something.

Of course not. But the shareholder value!

Because of Windows.

They also apparently didn’t do any input validation. This is why a faulty config was able to even trigger all of that.

Some nice ideas in there.

Only the “markdownquote” thing is kinda pointless, especially since they mention it’s mainly used in vim. Because vim can do exactly that already without the need of an external script. Do ctrl+v, mark the lines you want, press “I” (capital i), insert the desired thing, press esc and voila… all the selected lines are now prepended with the desired thing.

edited to make my comment sound less harsh: Nothing wrong with building your own solution if that feels better to oneself though :-)