tmux VS Tmuxinator

tmux2k was inspired by dracula/tmux.

Tmux (which Vim runs inside): https://draculatheme.com/tmux

Let's go over how to install a package. I really like the dracula theme plugin. To install it, I have the following in my tmux config:

dracula theme

I doubt that would be possible with tmux's built-in zoom functionality (if it is, I'm not aware). You can use tools such as tmuxinator to create cusotm layouts, but I think "zoom" in tmux means "cover the whole window"

mprocs looks pretty cool. In the past I've used Tmuxinator or Tmuxp configs for stuff like that.

Tmuxinator allows you to more-easily manage your tmux sessions using a single command. munsking explains, "without it, tmux is pretty much the same as screen for me… pseudo example: 'tmuxinator clients' would open a tiled window with 16 windows with ssh to 16 clients and sync input after login."

- https://github.com/tmuxinator/tmuxinator

or use tmuxinator which uses a similar yaml format.

Tmux, is well.., tmux. Tmuxinator makes it manageable, but the "layout" definition is far from readable, and copying errors from history to your clipboard, is a true pain in the ass.

I think you can achieve this using tmuxinator (and much more)

I recall that https://github.com/tmuxinator/tmuxinator purports to fill a similar need (“declaratively define tmux layouts”) but the fact it takes a Ruby dep, and doesn’t (IIRC?) have the in-your-face left hand index panel always made me shy away from exposing it to unsophisticated pairing partners. “First, install Ruby” is a helluva steep starting point for some random DevOps sitting on their piece-of-shit laptop inside a bank!