On Mon 23 Sep 2019 at 06:10:22 (-0500), Richard Owlett wrote: > On 09/23/2019 03:36 AM, Curt wrote: > > [snip] > > > > Honestly, I took the name 'script'.py for a metasyntactic variable. > > Yes that was my intention. My question was concerning all scripts. > Mentioning the specific script would be "noise".
Sure, that's the sense in which I used it. Only my parethesised sentence considered the word script more as a literal, and even there it's really being used as a metasyntactic variable for any generic name like "script", "myscript", "main", "runme", etc for the principal script, as opposed to the helper scripts that you mentioned. I would keep all these out of $PATH. Also in my "second category" would be scripts like, eg, spludge-2.5-linux-x86 and spludge-2.5-linux-64 which install the program called spludge. They would be run infrequently (possibly just once), so running them from an out-of-PATH location via bash or python would be appropriate. OTOH in my first category would be scripts that have "meaningful" names like append-silence, assemble-from-cache, background-changer … to quote a few examples that are in my PATH. > > I > > can't see offhand why it couldn't easily be changed if it wasn't and > > the OP actually downloaded some python script called "script." But that doesn't make any difference to its function, which (in my book) would determine whether to place it in my PATH or not. That PATH/non-PATH distinction was the reason for my post, not whether the script had this name or that. Cheers, David.
