I also make sure that I understood the ones that I keep. Now that I'm older and wiser (am I? :D), I have deleted the configs that I don't need. When I started using tmux a few years ago, I copied + pasted much of my tmux config from random sites I found from the internet. I remember the times I was staring at a blank MS Word when having to write a report or a blank Strathmore Paper when having to draw a scene - it can be intimidating having to fill up your config file from a blank slate. The possibilities are endless.Įndless possibility is not always a good thing. So what can you put inside the tmux config file? Anything. It is a path to a file where you enter your own configurations so next time you launch tmux, it executes everything inside that config file. nf in the HOME path ~/.nf (technically tmux looks for /etc/nf first, then ~/.nf, but the former is best left untouched).Ī. When you start a tmux session, tmux looks for a file named.
To do this, we need to configure the tmux config file. It would be nice to be able to change some of the default configs into something that are more intuitive to me, the user. There is nothing about " and % that are associable to horizontal / vertical splits. I also found commands like the split commands Prefix + " and Prefix + % are not intuitive. The letter b is positioned at a weird distance from the ctrl button. For example, I never understood why tmux uses Ctrl + b as a prefix. When you start using tmux, you may think that some of tmux's keys are not intuitive or straight-up uncomfortable to reach. It is highly recommended that you either read my previous article or are already familiar with how tmux works. No, tmux can't do your chores or make your wildest dreams come true, but tmux probably can make your wildest terminal multiplexing dreams come true :D. Whenever you thinking "Can Tmux can do that?" when reading this article, the answer is, 90% of the time, "Yes, tmux can do that!". Here you will learn useful tmux shortcuts you might not even know exist. My hope is that by exposing a list of my personal tmux configurations and my reasoning behind them, you will see a general pattern and understand it enough to make tmux your own. Here you'll learn some configurations that I use.
TMUXINATOR LAYOUT OPTIONS HOW TO
However, in that article, I didn't cover much how to customize tmux. In the previous article, you learned how to use tmux: what tmux is, how to manage multiple terminals, and how to use tmux's powerful features. This article is part 2 of my tmux series. If you want to increase your productivity I would suggest learning more about tmux.Configuring Your Tmux to Be Even More Awesome Tmuxinator is quite simple so there isn't much more to cover. In general it's recommended to keep it simple, especially if you are starting out with tmux, but if you want to try more complex sessions, make sure you use different leader keys for each layer!įor more info on using tmuxinator, the readme on their GitHub repo here contains documentation. The tmuxinator session is attached to netkit machine sessions, and one of the netkit machines (a) has its own tmux session open. In theory you can nest multiple layers of sessions - for example here I have a tmux session on my host, with a pane SSHd into an Ubuntu VM, which has a tmux session started by tmuxinator.
If you use the same leader key in your tmux config, this will conflict and it is recommended to change it! If you haven't changed your tmux config, the leader key will be ctrl + b - so you don't need to worry about this. Using tmuxinator with netkit will give you at least two layers - as you have the main session - created with tmuxinator, which has panes that are attached to sessions which are created for the Netkit machines.īy default, the netkit machine sessions will use a leader key of ctrl + d. This can get very annoying, so it is recommended to use a different leader key for each layer of nesting. This means if you had the same leader key for an outer session and an inner session, you would have to hit the leader key twice in a row to send commands to the inner session. You need to remember when you nest sessions, that the outer session will intercept key presses first, and process them before they are passed to the next inner layer. This example would connect you to the pane for machine b when you run tmuxinator start abr.
0 kommentar(er)
