AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Tmuxinator new side pane8/16/2023 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 Comments
Read More
Leave a Reply. |