3 ms·
What I do, and would recommend, is spin up vim or emacs as a daemon, then connect to it as a client in one or more tmux windows. That way, you can yank/put eas
by kornish 10y ago
What I do, and would recommend, is spin up vim or emacs as a daemon, then connect to it as a client in one or more tmux windows.
That way, you can yank/put easily using the usual shortcuts from any tmux window to any tmux window. Then, it's usually easiest to only use intra-process pane splitting (keeping it all in vim or emacs) unless you need to do something that doesn't follow a perfect division, like:
top half vim / bottom left vim / bottom right trailing logfile
or something.
More than happy to write a blog post, if you're interested.
- nilkn 10y agoI already use tmux and vim regularly but I'd definitely be interested in a blog post on this technique.
- pfranz 10y agoInteresting to run it as a daemon and connect. I'd be curious to see how you set it up and use it in practice. Whenever I use vim splits I'm almost always diffing left and right. So, nothing fancy.
- kornish 10y agoDefinitely. If you shoot me an email (hello@tedkornish.com) I'll let you know when the post is up. As a disclaimer, I use emacs with evil mode, not vim proper, so the command is just emacs --daemon=myproject Then it's just emacsclient -nw -s myproject ./directoryhere to connect, and the first part of that can be aliased away. Not 100% sure that vim has a good daemon/client mode, but I seem to recall something existing along those lines. It can be extremely useful to have multiple collections of editor panes set up, each in a different part of the codebase, and the ability to switch back and forth quickly with tmux - really helps for debugging and keeping organized.