Customizing my Linux terminal with tmux and Git

Set up your console so you always know where you are and what to do next.
85 readers like this.
woman on laptop sitting at the window

CC BY 3.0 US Mapbox Uncharted ERG

I use GNOME Terminal, mostly because it is my distribution's default. But what happens inside my terminal is far from "default." Before I get into how I customize it, here is what it looks like:

Start at the bottom

I use tmux, a terminal multiplexer technology, to manage my terminal experience.

At the bottom of the image above, you can see my green tmux bar. The [3] at the bottom indicates this terminal is the third one: each terminal runs its own tmux session. (I created a new one to make the font larger, so it's easier to see in this screenshot; this is the only difference between this terminal and my real ones.)

The prompt also looks funny, right? With so much information jammed into the prompt, I like to stick in a newline so that if I want to do impromptu shell programming or write a five-step pipeline, I can do it without having things spill over. The trade-off is that simple sequences of commands—touch this, copy that, move this—scroll off my screen faster.

The last thing on the line with the content is Aleph null, the smallest infinite cardinality. I like it when it is obvious where a content line ends, and when I realized that both Aleph and subscript 0 are Unicode characters, I could not resist the temptation to make Aleph null part of my prompt. (Math nerds, unite!)

Before that is my username; this is moderately useful since I use the same dotfiles (stored in Git) on multiple machines with different usernames.

Before my username is the last component of the directory I am in. The full path is often too long and useless, but the current directory is invaluable for someone, like me, who constantly forgets what he's working on. Before that is the name of the machine. All my machines are named after TV shows that I like. My older laptop is mcgyver.

The first bit in the prompt is the bit I like the most: one letter that lets me know the Git status of the directory. It is G if the directory is "(not in) Git," K if the directory is "OK" and nothing needs to be done, ! if there are files unknown to Git that must be added or ignored, C if I need to commit, U if there is no upstream, and P if an upstream exists, but I have not pushed. This scheme is not based on the current status but describes the next action I need to do. (To review Git terminology, give this article a read.)

This terminal functionality is accomplished with an interesting Python utility. It runs python -m howsit (after I installed howsit in a dedicated virtual environment).

You can see the rendering in the image above, but for completeness, here is my PS1:

[$(~/.virtualenvs/howsit/bin/python -m howsit)]\h:\W \u ℵ₀  
What to read next
Moshe sitting down, head slightly to the side. His t-shirt has Guardians of the Galaxy silhoutes against a background of sound visualization bars.
Moshe has been involved in the Linux community since 1998, helping in Linux "installation parties". He has been programming Python since 1999, and has contributed to the core Python interpreter. Moshe has been a DevOps/SRE since before those terms existed, caring deeply about software reliability, build reproducibility and other such things.

Comments are closed.

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.