vim + i3
Moving between i3 windows with vim like key patterns.
In vim everything turned off:
No line numbers, no tabs, only the one file open.
Not sure if this is the best setup but I’m stuck with this cause everything else is breaking the flow.
preciz
0
RobertDober
It is so great to see how many of us are there 
and I would not say still but already 
My workflow depends totally on neovim (using lua heavily and waaaay too bloated vimscript) integrating to tmux with things like system("tmux send-keys....'you get the idea'")
NERDTree, lots of Tim Pope’s plugins (Fugitive, vim-surround,…) fuzzy-vim
my big issue is screen redrawing I just need to minimize remaximize my screen whenever I switch a tmux window and that on iterm2 as well as gnome-terminal, I just did not see anybody having this problem so it’s probably a little bit OT 
2
sodapopcan
I’ve never had this problem on iTerm2 but I have redrawing problem s often enough. If it’s just Vim, :redraw! always does the trick which you can just make a mapping for (or add :redraw! at the end of a commonly use mapping, like after save).
0
sodapopcan
What do you like about Vim over Emacs? I ask because I’ve known people who have made the switch from Vim to Emacs and seem happier and there are some things about Emacs that seem attractive over Vim.
0
sodapopcan
It’s interesting to see all the nvim users. I used nvim briefly around when it came about but switched back to Vim8 once it came out. What are the reasons people prefer nvim? The LSP certainly seems promising. I also found it kind of shitty how Bram refused the jobs PR and then just implemented it himself when people started using nvim. Maybe he good reason? I dunno. He’s absolutely allowed to do what he wants but I still thought it was still a little lame.
0
John-Goff
I switched to nvim around 0.2, so about 4 years ago now. There’s a few reasons why I have stuck with neovim over vim
- community based development model. I don’t like the fact that Bram must agree a feature is good before it’s even considered. See terminal, async jobs, floating windows, etc.
- standard xdg home based config. Not a massive deal but it makes everything easier to deal with and more cohesive.
- lua scripting. I don’t write a ton of vim script stuff but when I do it’s much nicer to work in lua.
There’s other benefits too, like saner defaults and dropping a ton of legacy stuff which just slowed down development, but most of the other changes affect neovim developers more than they affect me.
Basically for me it boils down to the fact that there’s no downsides to picking neovim over vim and plenty of upsides.
2
rashidwinter
For sure! I’ve used vi for so many years (decades really) my fingers just know what to do. I’ve tried other editors but always return to vi 
1
joaquinalcerro
baldwindavid
I jump back in there from time to time. It’s pretty nice at this point. My issue is I’m using the vscode elixir-ls extension. For whatever reason, my cpu spikes to 300-500% with about every action so it’s just unusable. I haven’t had a chance to dig in so don’t know if it is something unique to my machine or not. I haven’t seen the same issue testing in vscode with the same extension though. Otherwise, I’d probably try to make it my daily driver. It’s native (fast), real vim, and has ever growing support for both viml and vscode extensions.
0
joaquinalcerro
Thanks for the feedback. I like the project for the reasons you mention but haven’t been able to set it up correctly because I never used vscode so it will take some time to understand how to configure it properly or at least how I have me current neovim setup. Best regards,
0