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.
I know that some vim users prefer to run commands from inside vim. Is that the type of people this project is aimed at?
Long answer: Even though I'm also using (neo)vim inside a tmux, there are a few caveats that I need from tmux.
The main one is while tmux is pretty much available everywhere, it's doesn't support Windows. My work machine (as provided by the company) are running on Windows and a lack of terminal multiplexer which prevented me to have the unified development environment across multiple setups from my MacBook to my Raspberry PI Zero.
Also, with one binary, you would hit 2 birds with one stone. Given that you're not doing anything fancy beside basic terminal multiplexing.
I imagine having tmux in vim instead of vim in tmux might resolve that issue for me. I'm curious to try this for that reason.
I havent switched to neovim yet, but for a lot of my work I have very long running vim sessions that i reconnect to. I find it much nicer having a single system managing my environment than multiple different layers.
Also tmux is a terminal emulator, where-as dtach passes through, and I find a lot less weird color handling & other bugs with dtach.
With (neo)vim as terminal multiplexer, you would have a totally different ecosystem where you can integrate various plugins to it. Like tmux has TPM, (neo)vim would have vim-plug (or many more plugin managers) to help integrate another plugins and tailor to your setup.
Is there a point to switching to nvim now though, with vim 8 available everywhere? What does nvim brings?
Doesn't support detachable sessions yet, though. That's a core requirement for me, so it'll need to wait for Neovim 0.7.
with tmux i can just relogin and attach
