Re: Command substitution with null bytes generates warning

[L. A. Walsh]

The script is 5 years old.  I don't remember any of the
design decisions that went in to it -- so you wanna pick it apart, go
ahead.  I am already quite able to do so myself on stuff I wrote
even 3 years ago, often, so 5 years, hey, go for it.

I wasn't even using aliases to help my coding back then or have
"include" files.  Shame bash doesn't have those natively.

(include files only get included once by default and can be
specified by a path relative to PATH...)

BTW, did I mention that was only 1 version of that and that
it was intended as a one-of hack?