Archives/rwxrob-dot
2
0
Fork 0
mirror of https://github.com/rwxrob/dot synced 2024-11-04 18:00:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
5df41e7f3a
rwxrob-dot/tmux
History
Rob Muhlestein 9eb7bf9937 add a bunch of stuff
2023-08-23 04:41:35 -04:00
..
.tmux-live.conf Add a bunch of random updates 2022-10-08 03:27:01 -04:00
.tmux-plain.conf Rebase 2022-02-09 02:29:05 -05:00
.tmux.conf add a bunch of stuff 2023-08-23 04:41:35 -04:00
README.md Rebase 2022-02-09 02:29:05 -05:00
setup Rebase 2022-02-09 02:29:05 -05:00

README.md

TMUX Terminal Multiplexer Configuration

TMUX is the most powerful multiplexer on the planet. But one of the most annoying things about it is that rather than choose backward-compatible key bindings with screen they choose to do something entirely different. I might understand why they did it, but I don't agree with it. Therefore, the tmux.conf configuration file is designed with two top priorities in mind:

  1. 100% screen muscle memory
  2. Vim-bindings for pane navigation and resizing

Live Configuration

The live.conf file is for those who wish to replicate how I run one TMUX session within another (TMUX-ception). This allows me to have WeeChat running in the bottom parent pane and an entire additional TMUX session in the lower pane. This allows me to create new windows and panes freely without messing with the top of the computer screen dedicated to chat (but requires using tmuxin when starting up a tmux within a parent tmux, see below).

The live configuration also dedicates the entire status line to information provided for the stream and not the current editing session. Currently, that is a date and time and space for a pomo session. The nested session has its own status line.

In order to avoid the troubles remembering what all the keystrokes are for everything I only use the default C-b meta key for the parent session and my normal C-a (same as screen) for the nested session. Since I never really use remote TMUX sessions --- preferring instead to quickly open up another local pane with a remote connection in it --- I never regret not having C-b to handle the nested remote TMUX session scenario.

Use tmuxin to Enable TMUX-ception

Remember to unset TMUX to allow starting the nested TMUX session. To make it easier tmuxin can be used instead of tmux.