Start all of your commands with a comma (2009)
rhodesmill.org
Start all of your commands with a comma (2009)
1–10 of 130 posts
Re: Start all of your commands with a comma (2009)
#2This is a good trick to avoid collisions with system commands. Anytime you add one of your own executables to PATH, prefix it with a comma (,). This way you avoid name collisions and have a handy way of seeing what commands are available on your system using tab completion (, then tab lists all of your personal executables)
Re: Start all of your commands with a comma (2009)
#3This is a good trick to avoid collisions with system commands. Anytime you add one of your own executables to PATH, prefix it with a comma (,). This way you avoid name collisions and have a handy way of seeing what commands are available on your system using tab completion (, then tab lists all of your personal executables)
[deleted]
Re: Start all of your commands with a comma (2009)
#4Cool.
I have a script that creates new ~/bin scripts that checks for collisions locally (functions, builtins, and executables) and in linux distros.
For example, I have a ~/bin/up script on every box and platform to install updates. So far so good on collisions.
Re: Start all of your commands with a comma (2009)
#5No post body was provided.
Re: Start all of your commands with a comma (2009)
#6Quoted post unavailable.
That was long enough ago that I think it’s worthy of being reposted. It was new to me.
Re: Start all of your commands with a comma (2009)
#7Quoted post unavailable.
Oh no it was posted over 2 years ago
Re: Start all of your commands with a comma (2009)
#8Clever trick. Too bad there's no good way to namespace commands. It would be interesting if you could have, for instance:
$ mkdir -p /tmp/bin/my
$ printf '%s\n%s\n' '#!/bin/sh' 'echo hello' > /tmp/bin/my/hello
$ chmod 755 /tmp/bin/my/hello
$ PATH="/tmp/bin:$PATH"
$ my/hello
helloRe: Start all of your commands with a comma (2009)
#9I use this method for aliases in my `.*rc` file so I can remember what the heck I called things. Otherwise, I forget whether I have to type something like `COMMANDNAME-log` or `log-COMMANDNAME` or some other weird combo like `print-COMMANDNAME-log`. With a comma, I type `,` and get all of my custom commands listed easily.
Re: Start all of your commands with a comma (2009)
#10Clever trick. Too bad there's no good way to namespace commands. It would be interesting if you could have, for instance: $ mkdir -p /tmp/bin/my $ printf '%s\n%s\n' '#!/bin/sh' 'echo hello' > /tmp/bin/my/hello $ chmod 755 /tmp/bin/my/hello $ PATH="/tmp/bin:$PATH" $ my/hello hello
Just add another comma. Of course, this needs some deeper magic to work :)
,my,hello