Neovim vs VSCode Neovim - what are the tradeoffs?

• Vim

  54 14,034 9.6 TypeScript

  :star: Vim for Visual Studio Code (by VSCodeVim)

  

  What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

• CodeRabbit

  coderabbit.ai featured

  CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

  

• nvim

  7 4 8.0 Lua

  neovim config (by snelling-a)

  Too late

• my_neovim_config

  1 1 4.0 Lua

• lsp-zero.nvim

  132 3,892 8.8 Lua

  A starting point to setup some lsp related features in neovim.

  All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

• NvChad

  190 25,112 8.7 Lua

  Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.

  

  I just recently moved from VS Code to Neovim. I tried to do that a couple of months ago but I couldn't get the configs right. Then I found NvChad and I was pulled in. I'm a customization freak, so I ended up ditching it because I was having trouble customizing its defaults and finally had success. Here are is what I learned about making that move:

• null-ls.nvim

  165 3,554 0.0 Lua

  Discontinued Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.

  All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

• trouble.nvim

  60 5,661 9.5 Lua

  🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.

  All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• nvim-treesitter

  308 10,979 9.9 Scheme

  Nvim Treesitter configurations and abstraction layer

  

  All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

• lazy.nvim

  137 15,249 9.6 Lua

  💤 A modern plugin manager for Neovim

  This is it. One last tip is to use lazy as a package manager, it's much easier to use and very powerful. If you've seen these configs from theprimeagen, translating from packer to lazy is pretty easy.

• init.lua

  9 3,424 5.6 Lua

  This is it. One last tip is to use lazy as a package manager, it's much easier to use and very powerful. If you've seen these configs from theprimeagen, translating from packer to lazy is pretty easy.

• neogit

  55 4,162 9.9 Lua

  An interactive and powerful Git interface for Neovim, inspired by Magit

  

Suggest a related project