Alias, a case for it

The al alias is the pushd writer, and responsible for the aliases which use use that built-in to push the directory onto the stack and remove any duplicates. The current list:

• blog – my now-deprecated blogging location
• finance – and
• invest – two directories which should be merged
• js – where JavaScript development is taking place
• resh - which was manually created, to be cleaned up as below, and
• stone – which wasn't created with al, but started the cascade, breaking marty's threshold of three.

To see the current list:

$ alias | grep pushd

To reset the resh alias to the directory name:

$ resh; unalias resh; al

The alias is now reshoring, a bit longer, but that's the way to remember it.

The shorthand for G\rep A\lias. Replace the above with

ga pushd

A conventient counterpart is ta, which checks for types. Before appropriatting a name as an alias, e.g.

ta ga

The ja alias demonstrates the quoting escapes needed to put a sed command into an alias. In these cases, use a function to simplify the code.

A few aliases help with my "used-by, i-use" confusion:

$ ga use
alias i_use='fun_uses'
alias use_me='fuse'
$

Here's a self-refernential usage:

$ i_use fuse
fuse
needir
spaceit
$
$ use_me fuse
clf         set -- $( args_uniq $(fuse ${1:-clf} | field 1 ));
fapi            set -- $( args_uniq $(fuse $1 | field 1 | sed 4q ));
fapi            _fun_show fuse $1 | _trim_hash
fnuse       declare -f $1 $( fuse $1|field 1 )
fun_create          fuse eval | grep '()' | sed 's/ *()/ ()/; s/ *\$/$/' | awk '$4 ~ /()/'
fun_maker           set | fuse eval | grep ' () ' | field 1
fun_useme           fuse ${1:-ff} | awk '
fuse        local tmp=$( needir $HOME/tmp )/fuse.tmp;
fuse        local awk=$( needir $HOME/tmp )/fuse.awk;
fuse_lib                fuse $1 | sed "s/^/$1   /"
fuse_lib            foreach _fuse_one $( functions $1 ) | tee fuse.out | field 1 | uniq -c | awk '$1 < 2 { print $2 }';
fuse_lib            wc fuse.out 1>&2
isclf       set -- $( args_uniq $(fuse ${1:-$(myname )} | field 1));
sfuse       fuse $1
$

Worth noticing the difference in output format. e.g. use_me, namely fuse, shows the context where the function is used, "how am I invoked", and i_use, namely fun_uses, only shows the list of called functions.