I currently use tmux and vim all day every day, including as my dev environment (if I'm not in a browser). Are there any advantages to this?<p>My initial thought is that having vim inside a terminal session is a better organization model than having a terminal session inside of a vim pane, but maybe that's just because it's how I've worked for 20 years so it's what I'm used to.<p>I know that some vim users prefer to run commands from inside vim. Is that the type of people this project is aimed at?
nvim inside of tmux is my go-to development environment (i.e. <a href="https://matt-w.net/blog/workspace-management/" rel="nofollow">https://matt-w.net/blog/workspace-management/</a>), so I'll definitely need to check this out.<p>Doesn't support detachable sessions yet, though. That's a core requirement for me, so it'll need to wait for Neovim 0.7.
I use vmux (<a href="https://github.com/jceb/vmux/" rel="nofollow">https://github.com/jceb/vmux/</a>) to redirect all files opened for editing (via nvim some_file.ext) from any tmux window to a single Neovim session.
Honest question: I don't question the positive impact nvim had on vim's development and improvement. It really fostered new ideas and was key in pushing parallel module runtime.<p>Is there a point to switching to nvim now though, with vim 8 available everywhere? What does nvim brings?
While tmux has issues this would likely be the opposite of what I want because now my processes are reliant on vim. There is zellij if you want a fast Rust-based alternative to tmux.
I get that this is under development, but at this point is this really more effective or smoother in terms of workflow than just using standalone neovim and tmux?