View source for Jumping to frequently used folders and automating environment setups


[[Category:Containers and Virtual Environments]]

When you have several different projects to manage, it's likely that each of them has different requirements in terms of environment, packages installed, and so on. Ideally, all of these environments should be isolated from each other in order to avoid problems with dependencies. A simple example of this happens with Python projects, which should have dedicated&nbsp;<code>conda&nbsp;</code>or<code>&nbsp;venv&nbsp;</code>environments.

The goal of this simple guide is to show how to setup simple bash scripts that allow to quickly jump between different projects by automatically changing folders and activating the correct environment via a custom single-word command (an <code>alias</code>). N.B. All of the code in the snippets below should be in your&nbsp;<code>.bashrc </code>or .zsh<code>rc</code>&nbsp; files.

The first step is to setup a so-called&nbsp;<code>mark.&nbsp;</code>At a high level, this is basically a pointer that marks the project directory and tells the system where to move from an arbitrarily different directory. This can be set by simply typing&nbsp;<code>mark&nbsp;</code>in the project directory. The simple functions&nbsp;that do this are
<pre>export MARKPATH=$HOME/.marks
function mark {
&nbsp; &nbsp; &nbsp; &nbsp; mkdir -p "$MARKPATH"; ln -s "$(pwd)" "$MARKPATH/$1"
}
function unmark {
        rm -i "$MARKPATH/$1"
}
function marks {
&nbsp;       # for linux (currently commented out)
&nbsp;       # ls -l "$MARKPATH" | sed 's/&nbsp; / /g' | cut -d' ' -f9- | sed 's/ -/\t-/g' && echo

        # for mac
&nbsp;       \ls -l "$MARKPATH" | tail -n +2 | sed 's/&nbsp; / /g' | cut -d' ' -f9- | awk -F ' -> ' '{printf "%-10s -> %s\n", $1, $2}'
}
</pre>

After this we can setup the&nbsp;<code>jump&nbsp;</code>command to move around the filesystem to previously set marks.
<pre>function jump {
       cd -P "$MARKPATH/$1" 2>/dev/null || echo "No such mark: $1"
}
</pre>

The last step is to simply setup an alias that jumps to the correct mark and activate the relevant (in this case Python with Conda) environment:
<pre>alias CUSTOM_NAME="jump MARK_NAME; conda activate ENVIRONMENT_NAME"
</pre>