11–20 of 21 posts
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. Is there a point to switching to nvim now though, with vim 8 available everywhere? What does nvim brings?
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? 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…
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 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?
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.
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?
> is this really more effective or smoother in terms of workflow than just using standalone neovim and tmux? No, but this would help fill in the gap that tmux lack for some use cases. So, it would all depends on what are looking for from it. 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…
with tmux i can just relogin and attach
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? 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…
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? 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…
One disadvantage of the Tmux approach is that if you have multiple nvim windows open, you can't copy from one to another.
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? 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…