As I first started using Linux, the terminal was “just there”, it was a given. Need to run some commands? Open the terminal and type away.

Think about it for a second. You clicked on an icon or pressed some hotkey, and a new window appears on your screen: A familiar prompt, maybe preceded by a MOTD, and you can start processes, read their output, move around in the filesystem etc.

• What just happened?
• How does this new window know how to interpret a CTRL+C?
• Where are you actually typing?

In this post I’ll only talk about how I use tmux. Hopefully you’ll find something to assimilate in you own workflow!

This is not a guide or a tutorial on using tmux.
Read the wiki’s Getting-Starderd page for a detailed explanation on how tmux works
Check out my .tmux.init for the actual configuration, and tmux_init.sh for the session-init script

let’s get started!

the problem

I just connected to a remote machine. Maybe I just have to run a couple commands, maybe I am logging in with a functional user… but for whatever reason I cannot load my trusty dotfiles on it.
No biggie, let’s get to work!

z
# z: command not found
l
# l: command not found
ll
# ll: command not found

Using HUGO instead of a fancy CMS, it took no time at all.

Goal

Use an already overworked raspberrypi to serve a staticly generated Blog
If you are reading this, it means it worked!