Re^3: Wrong idioms

Hm, I think '-' can cause problems with getopts sometimes.

Oops! Starting filenames with '-' is just asking for trouble. Your life will be least painful if you start names with [a-z_], use only one '.', don't make them too long, and don't rely on case differences alone. If you find yourself wanting arbitrary filenames, either never pass them to other software, or consider using a database.

Comment on Re^3: Wrong idioms Download Code

Replies are listed 'Best First'.
Re^4: Wrong idioms by thargas (Deacon) on Apr 03, 2013 at 12:14 UTC
I remember a colleague who used to create files named "-i" in directories he wanted to protect. That way, when you did "rm *", the file list expanded into "rm -i ..." and you got prompted for each file. I'm not recommending it, but he liked it.	[reply]
Re^5: Wrong idioms by Your Mother (Archbishop) on Apr 03, 2013 at 14:21 UTC
The first thing I do when given a new shell account is alias `rm` to `rm -i` to protect everyone from me. :P	[reply] [d/l] [select]
Re^6: Wrong idioms by thargas (Deacon) on Apr 09, 2013 at 13:16 UTC
I can understand that, but since I put almost everything under git, it's less interesting to me. However, personally, as part of my standard setup, I unalias all the common commands, in case some (IMHO misguided) sysadmin decides to inflict behaviour-changing options on standard commands via aliases. I'm all for a customized environment, but the standard commands (like ls, rm, cp, mv, ...) have to work the same or stuff breaks. Instead, I make my own shell functions, like `e` which is a wrapper around whatever my favourite editor is with name-remembering. I don't make an alias or function which has the same name as one of the usual commands as I've wasted too much time trying to figure out why a pipeline wasn't working due to `ls` not really being `ls`.	[reply] [d/l] [select]