On Sun, Mar 16, 2025 at 04:39:33 +0700, Robert Elz wrote: > ps: to anyone out there still reading this, when writing sh code, don't > lapse into writing C instead, in sh, when using quotes, use '' (or \) > whenever the quoted text is to be treated literally, and "" only when > you are expecting expansions in the included string
I'm still reading this, or at least skimming over it. The problem is that certain people who are posting here aren't writing shell code. They're writing *shells*, or rather things that should not be shells but are for some reason implementing parts of shells internally. And those people don't want to hear *anything* we have to say about writing shell code. I would rather throw an error message than implement certain parts of shell compatibility. I would advise anyone writing a not-a-shell to do something similar. I wish real shells could do that. It would (eventually) clean up *so* many broken scripts.
