5 ms·

I love Neovim. I switched from VSCode and never looked back, it's just so much more efficient to just do everything with your keyboard. In case someone is inter

I love Neovim. I switched from VSCode and never looked back, it's just so much more efficient to just do everything with your keyboard. In case someone is interested how to do the things you're used to from VSCode, I created some videos: https://youtube.com/playlist?list=PLu-ydI-PCl0OEG0ZEqLRRuCrMJGAAI0tW https://youtube.com/playlist?list=PLu-ydI-PCl0OEG0ZEqLRRuCrM...

mraza007 5y ago
Thank you for making these !!!
- davidkunz 5y ago
  Glad you like them!
efficax 5y ago
Funny, I switched from neovim to VSCode + the vim plugin. Sure, it doesn't have everything I would do with vim supported, but it's enough and overall it's a better experience
- Jenk 5y ago
  I've started using the vscode neovim plugin. It runs a headless neovim in the background so you get literally everything that both editors provide in one. It's not 100% flawless but it is damn good. I used to flip between the two anyway - if I needed a better intellisense for, say, a large typescript project, then vscode won, everything else was nvim. Now I have the intellisense of vscode ontop of neovim.
  - ibraheemdev 5y ago
    For anyone wondering: https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim
  - EvanDotPro 5y ago
    As a LONG time Vim (now Neovim) user, I've been pretty curious to try this as it would allow me to retain some of my beloved plugins and custom config without the effort of trying to find replacements or reproduce my config stuff. I imagine I could also get rid of most of the language server / autocomplete / code navigation type stuff that comes easier in VS code. It could potentially be the best of both worlds if it's done as well as I'm hoping it is. I haven't tried it yet, but my main concern is that VS Code probably has a lot of keyboard shortcuts (e.g., C-v for visual block mode) that I'd have to reassign, which could potentially be a bit of a pain initially. Mind sharing any pros/cons you've run into with the Neovim plugin so far?
    - liveranga 5y ago
      I've been using it for a couple months now. It's really quite good and the plugin disables most (all?) of the clashing hotkeys. The only thing I've noticed is sometimes there's a delay on the Esc key detection to exit insert mode. That could be my binding of CapsLock to Esc/Ctrl though (with a combination of xmodmap and xcape). I'm also a long time vim user but this has made it bearable to use the same editor as the rest of the team (engineers who need to code, not software engineers) so that they understand what's happening when pair programming etc.
    - jay-aye-see-key 5y ago
      I started with vscode but moved to (neo)vim 2 or 3 years ago. Last year I experimented going back to vscode with one of the vim plugins. By default there are some conflicting keybinds like ctrl-o and ctrl-v, but these can be disabled in vscode settings.json so wasn’t a problem. The main feature that doesn’t work over the neovim-vscode rpc bridge is undo tree, that was important to me. You also have to put up with much slower start up times and slower syntax highlighting because vscode uses lsp highlighting. But the deal breaker for me was losing any vim plug-in with a ui component like fzf, fugitive, and the file tree I like (fern.vim). It might work for you, some coworkers switched from vim to vscode-neovim and were very happy with the compromise.
- thayne 5y ago
  I tried switching to VSCode with the vim plugin. but I got frustrated with vim keys that didn't quite work right on VSCode. And iirc configuring custom vim-style bindings was quite a pain. And then there were the neovim/vim plugins that I used that didn't have good equivalents in VSCode, especially that worked well with the vim plugin. Also VSCode is much, much more resource hungry.
  - CalChris 5y ago
    You were probably using the more popular vscodevim with its 2.7M installs. Try vscode-neovim with its merely 93K installs. vscode-neovim is designed for and requires neovim 0.5. I hate, hate, hated vscodevim but vscode-neovim is very good, very usable; I stopped using VSC altogether until vscode-neovim got real. It's not perfect, it still needs work on command mode, but it's quite usable. I even got rid of my other vims (MacVim, VimR, ...).
systems 5y ago
I am not sure how this is possible Editors like Vim, Emacs or VSCode are all about the plugins I use emacs for org mode And VSCode for everything else, because simply most proramming languages have their main plugins on VSCode The only way you can move from VSCode to neovim is, if you dont care about the plugins Why would you VSCode if not for the plugins
- davidkunz 5y ago
  Regarding programming languages, the answer is the language server protocol (LSP), an editor-agnostic way to use IDE-like features, originally developed for VSCode. Works for both Neovim and VSCode (and many others). Somewhat ironic that one of VSCode's best inventions is the one which made me switch away from it.
  - qudat 5y ago
    I just switched from 0.4 to 0.5 specifically for LSP and treesitter support. There is zero difference between it and vscode for me now. Neovim 0.5 is a game changer and closes the gap between it and vscode.
  - robryan 5y ago
    Yeah LSP also makes Sublime viable going forward where it otherwise probably would have fallen behind.
  - malloryerik 5y ago
    I saw it as Microsoft's signalling that they care more about being in the good graces of the wider developer community than about dominating the programming editor/IDE market. After all VSCode is free. I'd argue that giving away VSCode, LSP, Monaco (the base editor) and so on has been a successful means of redeeming their brand in the eyes of developers and really anyone who ever touches code. That could backfire if they took on an aggressively competitive stance. Letting LSP play nicely with other editors seems therefore good business for them. It also appears that as a profitable business, money Microsoft spends on VSCode might otherwise be spent as taxes?
lordgroff 5y ago
I'd love to go back to (neo)vim. I like vscode fine, but sometimes it sounds like a rocket is taking off from my laptop. However, the ability to have a full remote development environment act pretty much exactly like the local one is the absolute vscode killer feature. I just can't go back to a ssh season, cloning the plugins, and dealing with occasional latency.
pacomerh 5y ago
I've tried VSCode a couple of times but I always go back to Neovim. VSCode still depends on the mouse and that kills it for me. I haven't found anything I can't do in Neovim actually. I have a nice setup with Tmux and being already in the terminal is just too convenient and fun.

mraza007 5y ago

Thank you for making these !!!

davidkunz 5y ago
Glad you like them!

efficax 5y ago

Funny, I switched from neovim to VSCode + the vim plugin. Sure, it doesn't have everything I would do with vim supported, but it's enough and overall it's a better experience

Jenk 5y ago
I've started using the vscode neovim plugin. It runs a headless neovim in the background so you get literally everything that both editors provide in one. It's not 100% flawless but it is damn good. I used to flip between the two anyway - if I needed a better intellisense for, say, a large typescript project, then vscode won, everything else was nvim. Now I have the intellisense of vscode ontop of neovim.
- ibraheemdev 5y ago
  For anyone wondering: https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim
- EvanDotPro 5y ago
  As a LONG time Vim (now Neovim) user, I've been pretty curious to try this as it would allow me to retain some of my beloved plugins and custom config without the effort of trying to find replacements or reproduce my config stuff. I imagine I could also get rid of most of the language server / autocomplete / code navigation type stuff that comes easier in VS code. It could potentially be the best of both worlds if it's done as well as I'm hoping it is. I haven't tried it yet, but my main concern is that VS Code probably has a lot of keyboard shortcuts (e.g., C-v for visual block mode) that I'd have to reassign, which could potentially be a bit of a pain initially. Mind sharing any pros/cons you've run into with the Neovim plugin so far?
  - liveranga 5y ago
    I've been using it for a couple months now. It's really quite good and the plugin disables most (all?) of the clashing hotkeys. The only thing I've noticed is sometimes there's a delay on the Esc key detection to exit insert mode. That could be my binding of CapsLock to Esc/Ctrl though (with a combination of xmodmap and xcape). I'm also a long time vim user but this has made it bearable to use the same editor as the rest of the team (engineers who need to code, not software engineers) so that they understand what's happening when pair programming etc.
  - jay-aye-see-key 5y ago
    I started with vscode but moved to (neo)vim 2 or 3 years ago. Last year I experimented going back to vscode with one of the vim plugins. By default there are some conflicting keybinds like ctrl-o and ctrl-v, but these can be disabled in vscode settings.json so wasn’t a problem. The main feature that doesn’t work over the neovim-vscode rpc bridge is undo tree, that was important to me. You also have to put up with much slower start up times and slower syntax highlighting because vscode uses lsp highlighting. But the deal breaker for me was losing any vim plug-in with a ui component like fzf, fugitive, and the file tree I like (fern.vim). It might work for you, some coworkers switched from vim to vscode-neovim and were very happy with the compromise.
thayne 5y ago
I tried switching to VSCode with the vim plugin. but I got frustrated with vim keys that didn't quite work right on VSCode. And iirc configuring custom vim-style bindings was quite a pain. And then there were the neovim/vim plugins that I used that didn't have good equivalents in VSCode, especially that worked well with the vim plugin. Also VSCode is much, much more resource hungry.
- CalChris 5y ago
  You were probably using the more popular vscodevim with its 2.7M installs. Try vscode-neovim with its merely 93K installs. vscode-neovim is designed for and requires neovim 0.5. I hate, hate, hated vscodevim but vscode-neovim is very good, very usable; I stopped using VSC altogether until vscode-neovim got real. It's not perfect, it still needs work on command mode, but it's quite usable. I even got rid of my other vims (MacVim, VimR, ...).

systems 5y ago

I am not sure how this is possible Editors like Vim, Emacs or VSCode are all about the plugins I use emacs for org mode And VSCode for everything else, because simply most proramming languages have their main plugins on VSCode The only way you can move from VSCode to neovim is, if you dont care about the plugins Why would you VSCode if not for the plugins

davidkunz 5y ago
Regarding programming languages, the answer is the language server protocol (LSP), an editor-agnostic way to use IDE-like features, originally developed for VSCode. Works for both Neovim and VSCode (and many others). Somewhat ironic that one of VSCode's best inventions is the one which made me switch away from it.
- qudat 5y ago
  I just switched from 0.4 to 0.5 specifically for LSP and treesitter support. There is zero difference between it and vscode for me now. Neovim 0.5 is a game changer and closes the gap between it and vscode.
- robryan 5y ago
  Yeah LSP also makes Sublime viable going forward where it otherwise probably would have fallen behind.
- malloryerik 5y ago
  I saw it as Microsoft's signalling that they care more about being in the good graces of the wider developer community than about dominating the programming editor/IDE market. After all VSCode is free. I'd argue that giving away VSCode, LSP, Monaco (the base editor) and so on has been a successful means of redeeming their brand in the eyes of developers and really anyone who ever touches code. That could backfire if they took on an aggressively competitive stance. Letting LSP play nicely with other editors seems therefore good business for them. It also appears that as a profitable business, money Microsoft spends on VSCode might otherwise be spent as taxes?

lordgroff 5y ago

I'd love to go back to (neo)vim. I like vscode fine, but sometimes it sounds like a rocket is taking off from my laptop. However, the ability to have a full remote development environment act pretty much exactly like the local one is the absolute vscode killer feature. I just can't go back to a ssh season, cloning the plugins, and dealing with occasional latency.

pacomerh 5y ago

I've tried VSCode a couple of times but I always go back to Neovim. VSCode still depends on the mouse and that kills it for me. I haven't found anything I can't do in Neovim actually. I have a nice setup with Tmux and being already in the terminal is just too convenient and fun.