view .shell.d/99.prompt.bash @ 377:117e3c11d953

zprofile: introduce zprofile use El Capitan (OS X 10.11) introduces a system-level /etc/zprofile which uses a path_helper thing to mangle $PATH. Unfortunately, the way path_helper works, it forces /usr/local/bin and /usr/bin to the *start* of the PATH variable, which means that any PATH mutations I want have to run after /etc/zprofile calls path_helper. As such, move my path insertions into .zprofile{,-machine} rather than .zshenv{,-machine} so that I can still ensure my path entries are at the start of PATH rather than the end. This works because: > Commands are then read from $ZDOTDIR/.zshenv. If the shell is a > login shell, commands are read from /etc/zprofile and then > $ZDOTDIR/.zprofile. Then, if the shell is interactive, commands > are read from /etc/zshrc and then $ZDOTDIR/.zshrc. Finally, if the > shell is a login shell, /etc/zlogin and $ZDOTDIR/.zlogin are read. This means that non-login shells no longer pick up my custom PATH entries, but as I only use OS X as a desktop OS that seems like a workable tradeoff for now.
author Augie Fackler <raf@durin42.com>
date Sun, 31 Jan 2016 20:46:29 -0500
parents cb6704a7cef2
children
line wrap: on
line source

if [ "x`whoami`" = "xroot" ] ; then
    PS1='\[\e];\u@\h: \w [bash]\]\a[\h:\w] \[\e[31m\]\u\[\e[0m\]# '
else
    PS1='\[\e];\u@\h: \w [bash]\a\][\h:\w] \[\e[34m\]\u\[\e[0m\]$ '
fi

if [ "$TERM" = "rxvt" ] || [ "$TERM" = "xterm" ] \
  || [ "$TERM" = "xterm-color" ] || [ "$TERM" = "screen" ]; then
        export FANCYTYPE="YES"
else
        export FANCYTYPE="NO"
        PS1='[\h:\w] \u$ '
fi