Good topic and suggestions, all.

I’ve become much more reliant on my directory stack. Using one letter aliases to display them and to flip between them.

alias d='dirs -v'
alias 1='pushd +1'
alias 2= 'pushd +2'
alias 3='pushd +3' (etc.)


Recently I’ve started to save and restore the directory stack between shell session because I end up holding 5 or 6 useful locations in them. (Yes, my browser sessions have far too many tabs, too.)

Because shell sessions can terminate abruptly and lose your history and directory I like to do

PROMPT_COMMAND='history -a; dirs -l -p > ~/.bash_dirs_${HOST}'


and, during startup, check for the existence of the dir stack file and push each unique non-home entry onto the dir stack.

history -n ${HISTFILE}
if test -r ~/.bash_dirs_${HOST}; then
for d in `uniq ~/.bash_dirs_${HOST}` ; do
if test $d != $HOME; then
pushd -n "$d" > /dev/null
fi
done
fi


I just added colored man pages to my .zshenv; so much more legible!!

Thanks!!

@ ylee:

Thanks, autojump seems kinda cool. I will definitely check it out. :)

I am rather fond of :

shopt -s dirspell # Correct dir spelling
shopt -s cdspell # Correct spelling
shopt -s autocd # autocd

as well as the autojump command.

I also use in my .inputrc file:

# Pre-pend sudo to a command
"\C-s":"\C-asudo \C-e"

And btw thanks for export IGNOREEOF=1 . That is handy and I am not sure how I missed that all these years, lol.

@ Luke Maciak:
Ooups, sorry, there was no typo.

@ Alexei Matyushkin:

Which typo?

@ Guillaume:

Thanks, I fixed it. It should just be ignoreboth. :)

Thanks for the refresher! So next time it’ll be handy bash aliases and functions, right? :)

Scott

I don’t understand how this works:

# don't put duplicate lines in the history
export HISTCONTROL=ignoredups
# ... and ignore same successive entries.
export HISTCONTROL=ignoreboth

Doesn’t it mean that you override the HISTCONTROL value with the 2nd statement?

Hi, would you please fix a miscopypaste in cd - example, it now looks a bit confusing.

As for bash tips, I really like to put in command prompt the current dir’s git repo status and rvm gemset (if any). There are snippets over the internet in plenty.