Start all of your commands with a comma (2009)
rhodesmill.org
Start all of your commands with a comma (2009)
1–10 of 252 posts
Re: Start all of your commands with a comma (2009)
#2Neat trick! I don’t think I’ll namespace everything this way, because there’s some aliases and commands I run so often that the comma would get annoying, but for other less frequently used helper scripts then this will be perfect!
Re: Start all of your commands with a comma (2009)
#3Re: Start all of your commands with a comma (2009)
#4Re: Start all of your commands with a comma (2009)
#5Also, kudos to keeping it so concise and to the point, thats some prime writing.
Re: Start all of your commands with a comma (2009)
#6Re: Start all of your commands with a comma (2009)
#7Re: Start all of your commands with a comma (2009)
#8This is one of those ideas that is so simple and elegant that it makes you think “why did I never think of doing this?!” Neat trick! I don’t think I’ll namespace everything this way, because there’s some aliases and commands I run so often that the comma would get annoying, but for other less frequently used helper scripts then this will be perfect!
Re: Start all of your commands with a comma (2009)
#9If I introduce an alias (like `grep='grep --binary-files=without-match --ignore-case --color=auto`) that matches the name of a system binary - I probably do that intentionally.
And if I EVER need to call grep without my alias - I just prefix it with a backslash: \grep will search with case sensitivity and no color and will scan binaries.