Similar to the vim key concept which many people use comma for.
https://tuckerchapman.com/2018/06/16/how-to-use-the-vim-lead...
Start all of your commands with a comma (2009)
101–110 of 130 posts
Re: Start all of your commands with a comma (2009)
#102Clever 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
I think shells should support that, allowing you to do
$ my hello
It also could mean launching fewer processes (for the case where ‘my’ is a script or executable that looks up the location of ‘hello’ and launches it)
Re: Start all of your commands with a comma (2009)
#103Re: Start all of your commands with a comma (2009)
#104I misadvertantly lower cased my functions names when working on .net, but it made it super easy to find my code in the stack traces. (.net idiom is capitalism the first case of a function name). Usually the cause of stack traces was my code so it was an unexpected productivity booster.
Re: Start all of your commands with a comma (2009)
#105I use a similar trick for text expansion. All my abbreviations start with a semicolon (;). It’s on the home row, it never occurs at the start of a word in normal typing so I never have a false positive expansion, and it’s easy to remember.
Re: Start all of your commands with a comma (2009)
#106Can't you just declare:
my() {
script_name="$1"
script_path="$HOME/.local/bin/my/$script_name"
shift
$script_path "$@"
}
But it seems less weird than the comma.
-- EDIT --
With completion:
export MY_SCRIPS_DIR="$HOME/.local/bin/my"
_my_completions() {
if [ "${#COMP_WORDS[@]}" != "2" ]; then
return
fi
COMPREPLY=($(compgen -W "$(echo $(find "$MY_SCRIPS_DIR" -printf '%P\n' ))"))
}
my() {
script_name="$1"
script_path="$MY_SCRIPS_DIR/$script_name"
shift
$script_path "$@"
}
complete -F _my_completions my
After testing both, the comma win. Kiss, more flexible.
Re: Start all of your commands with a comma (2009)
#107Clever 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
Re: Start all of your commands with a comma (2009)
#108Meh. I'd prefer to have a path not in my PATH, and then explicitly call the binary with the full path .. and then append a #comment for easy recall with CTRL-R at some point later in the future.
A bit more fiddly perhaps, but future proof.
Re: Start all of your commands with a comma (2009)
#109clever idea, but does it need such a long post to describe?
If you're that pressed for time, you probably could get away with just reading the title.
Re: Start all of your commands with a comma (2009)
#110I have my bin folder in ~/usr/bin. The structure of ~/usr matches /usr and /usr/local, so I can build stuff into it with ./configure --prefix=$HOME/usr or similar. (You could of course do ./configure --prefix=$HOME, but then you run the risk of ending up with ~/share and ~/include and so on, something I don't want.)