about | blog | config | notes | github

This is configuration file for the interactive session for Zsh.

1. Interactive Configuration

1.1. Zsh Configuration

Configure how zsh remembers history.


Other useful defaults like auto-cd and turning off terminal beeps!

setopt AUTO_CD
unsetopt BEEP # turn of audible beeps

Setup Vim Bindings in Zsh.

bindkey -v

1.2. Load Autocompletion Engine

The directory we store the completion file will already exist due to the tangling of other zsh files.

autoload -Uz compinit && compinit -d "$HOME/.config/zsh/compdump"
autoload -U bashcompinit && bashcompinit

1.3. Source Aliases

source $HOME/.config/zsh/aliases.zsh

1.4. Configure SSH & GnuPG Variables

I don't know what to make of this. I thought I could have this code block in the ~/.zshenv file but I was unable to do so as it causing many issues. Seems like it needs to be set during an interactive session. Very strange indeed. Essentially this configured what pinentry program should be used for GnuPG and OpenSSH. Furthermore, it also tells OpenSSH that it should look into GnuPG to get the ssh authentication key.

export GPG_TTY=$(tty)
export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket);

1.5. Setup $PS1

There are basically two ways to set prompts. My old prompt was dynamic and required a function to run everytime it generated so we used the precmd code to generate it. However it introduces some problems with sh if you want to run it from zsh. Luckily, if you wish to run sh from zsh for whatever reason, one can simply override the hook before the command is run.

I however, am currently not using this setup, but I should configure it such that if I am in a pure terminal environment that I do in fact use my more verbose prompt. In my gui environment however, that level of information is overkill.

~ λ
export PS1="%F{blue}%~%f %B%(?.%F{green}.%F{red})λ%f%b "

This prompt below is my old setup

.-|ssh|-([email protected])-[debian::~/src/website]-<website.master>

Here is the generation function that builds the prompt.

function prompt_generate() {
    echo -ne "%B%F{cyan}.-"

    # Check if we are in an SSH connection
    if [ -n "$SSH_TTY" ]; then
        echo -ne "%F{black}|%b%F{blue}ssh%F{black}%B|%F{cyan}-"

    # user @ hostname
    echo -ne "%F{black}(%b%F{cyan}%n%F{white}@%F{magenta}%M%F{black}%B)"

    # distro :: current working directory
    echo -ne "%F{cyan}-%F{black}[%b%F{cyan}${DISTRO}"
    echo -ne "%F{white}::%F{blue}%~%B%F{black}]"

    if [ -d "`git rev-parse --show-toplevel 2> /dev/null`/.git" ]; then

        GIT_NAME=$(basename -s .git `git config --get remote.origin.url` \
            2> /dev/null)
        GIT_NAME=$(echo $GIT_NAME | sed -e 's|^.*:||g')

        if [ -z "$GIT_NAME" ]; then

        GIT_BRANCH=$(git branch --list --no-color | grep --color=auto '\*' \
            | sed -e 's/^\* //g' | head -n1 | tr -d '\n')

        # (yes/no add ; no commited)
        #YA=$(git status --porcelain 2>/dev/null| egrep "^M" | wc -l)
        #NA=$(git status --porcelain 2>/dev/null| egrep "^ M" | wc -l)
        NC=$(git status --porcelain 2>/dev/null| egrep "^(M| M | D)" | wc -l)

        # Use this info to construct our real status
        if [ $NC -eq 0 ]; then
        echo -ne "%F{cyan}-%F{black}<%b%F{$C}$GIT_NAME.$GIT_BRANCH%B%F{black}>"

    if [ -n "${ENV_NAME}${PIPENV_ACTIVE}${VIRTUAL_ENV}" ]; then

        echo -ne "%F{cyan}-%F{black}{%b%F{yellow}"

        if [ -n "$VIRTUAL_ENV" ]; then
            # Support both the old way of using venvs and new way
            echo -ne "venv:$(basename $VIRTUAL_ENV /.venv)"

        if [ -n "$PIPENV_ACTIVE" ]; then
            echo -ne "${MOD}pipenv"

        if [ -n "$ENV_NAME" ]; then
            echo -ne "$MOD$ENV_NAME"

        echo -ne "%B%F{black}}"
    echo -ne "\n"
    echo -ne "%F{cyan}\`--%B%F{white}> %{\e[0m%}"

I have this commented out, otherwise it would be using my old prompt. Maybe I should have this setup in only tty environments…

# precmd() {
#     export PROMPT=$(prompt_generate)
# }

1.6. Override LS Colors

The ls command is sometimes not colored properly (and I may have some custom colors that it doesn't like using for certain files by default) so lets override that here. Maybe I should have this in the ~/.zshenv file?

eval $(dircolors -b $HOME/org/config/lib/shell/lscolors)

1.7. Enter a Python Virtual Environment

If certain $VIRTUAL_ENV exist during session startup, then immediately jump into that python virtual environment.

if [ -n "$VIRTUAL_ENV" ]; then
    source ${VIRTUAL_ENV}/bin/activate

1.8. Emacs Vterm Shell-side Integration

Woah what is a function doing here!?

Well, VTerm requires some shell-side configuration in order to make use of its full functionality. It's quite powerful when as you can jump between prompts and other things. This is all done with the help of this function below, I'm keeping it here so that all shell-side code is in one place.

vterm_printf() {
    if [ -n "$TMUX" ] && ([ "${TERM%%-*}" = "tmux" ] || [ "${TERM%%-*}" = "screen" ] ); then
        # Tell tmux to pass the escape sequences through
        printf "\ePtmux;\e\e]%s\007\e\\" "$1"
    elif [ "${TERM%%-*}" = "screen" ]; then
        # GNU screen (screen, screen-256color, screen-256color-bce)
        printf "\eP\e]%s\007\e\\" "$1"
        printf "\e]%s\e\\" "$1"

This is used to pass information about user, hostname, and pwd back to vterm.

vterm_prompt_end() {
    vterm_printf "51;A$(whoami)@$(hostname):$(pwd)";

Adding another zsh hook to capture changes in directory I believe. This ultimately is used to set the buffer name for vterm in emacs buffer list.

autoload -U add-zsh-hook
add-zsh-hook -Uz chpwd (){ print -Pn "\e]2;%m:%2~\a" }

1.9. Setup Shell Functions

This will source the ZSH functions.

fpath=("$HOME/.config/zsh/functions" $fpath)

Now we have to this painful process of autoloading. Note:, that if the file being autoloading, includes functions, it will be to be autoloaded and run once like so autoload foo && foo.

Let's load the Python Venv Wrapper here.

autoload venv

1.10. X Window Terminal Info

The following code helps save X11 window information for every terminal. This can be used later to start new terminal sessions in those directories (Meant to be used with URxvt). In a nuteshell, the built-in cd is overridden to now save this window info.

function window_info() {
    echo "WINDOW_PWD='$(pwd)'";
    echo "VIRTUAL_ENV='${VIRTUAL_ENV}'";
function save_window_info() {
    window_info > /tmp/.wid_${WINDOWID}

Overrides default cd and also saves the terminal info at initial startup

if [ -n "$DISPLAY" ]; then
    # Build our custom cd
    function cd () {
        builtin cd $@
    # Every terminal should generate its id file on spawn
    if [ -z "$WINDOWID" ]; then
        # echo "Terminal doesn't have a Window ID!!!"

Created: 2021-11-13

Emacs 26.1 (Org mode 9.5)