8 ms·

I suggest you try something like LunarVim[1] or NvChad[2] for a ready-to use IDE-like neovim configuration. I had the same problem with configuring (neo)vim, i

I suggest you try something like LunarVim[1] or NvChad[2] for a ready-to use IDE-like neovim configuration. I had the same problem with configuring (neo)vim, it's simply too much work to get a reasonable IDE experience. Using an already well tested and documented configuration helped me to make the switch. [1] https://www.lunarvim.org/ https://www.lunarvim.org/ [2] https://nvchad.com/ https://nvchad.com/

cassepipe 3y ago
If only doing C and C++ dev work you can get pretty far with a very minimal vim config though But yeah, webdev had me switch to Lunarvim (my favorite among all those nvim distros)
retrochameleon 3y ago
I tried both and ended up using AstroNvim
lenkite 3y ago
[3] https://www.lazyvim.org/ https://www.lazyvim.org/
- EasyMark 3y ago
  lazyvim is definitely the one I found easiest of a bunch of these. I've been using it for a while now, I haven't tried in neovide though, I just did and it ran but when I did an update there was a compilation error (on mac). So maybe avoid an update there? :) It was easy to fix in standard iterm2 though (just resync).
unshavedyak 3y ago
Any idea if these would be problematic with Neovide?
- Ringz 3y ago
  Lazyvim runs fine
- zeroDivisible 3y ago
  LunarVim may require some symlinks but I've ran both with Neovide at some time. nvchad should work out of the box.
zamalek 3y ago
I would recommend against heavy-handed plugins, it's the reason I burned out on nvim and fled to helix. The thing about a breaking change in a plugin (like, oh, I don't know nvim-treesitter - likely the most installed plugin) is that you find out when you are about to do work/be productive. Keep nvim as minimal as possible IMO.
- gorjusborg 3y ago
  This guy gets it. I am also firmly in the vanilla config camp. Neovim is very usable out of the box. Once you are invested in the interface (modal editing) then look to get 'fancy'. I think the big config approach just tries to make the editor an IDE. You don't most of that to try it out. Start simple.
ivanjermakov 3y ago
I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro. I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim https://github.com/nvim-lua/kickstart.nvim

cassepipe 3y ago

If only doing C and C++ dev work you can get pretty far with a very minimal vim config though But yeah, webdev had me switch to Lunarvim (my favorite among all those nvim distros)

retrochameleon 3y ago

I tried both and ended up using AstroNvim

lenkite 3y ago

[3] https://www.lazyvim.org/ https://www.lazyvim.org/

EasyMark 3y ago
lazyvim is definitely the one I found easiest of a bunch of these. I've been using it for a while now, I haven't tried in neovide though, I just did and it ran but when I did an update there was a compilation error (on mac). So maybe avoid an update there? :) It was easy to fix in standard iterm2 though (just resync).

unshavedyak 3y ago

Any idea if these would be problematic with Neovide?

Ringz 3y ago
Lazyvim runs fine
zeroDivisible 3y ago
LunarVim may require some symlinks but I've ran both with Neovide at some time. nvchad should work out of the box.

zamalek 3y ago

I would recommend against heavy-handed plugins, it's the reason I burned out on nvim and fled to helix. The thing about a breaking change in a plugin (like, oh, I don't know nvim-treesitter - likely the most installed plugin) is that you find out when you are about to do work/be productive. Keep nvim as minimal as possible IMO.

gorjusborg 3y ago
This guy gets it. I am also firmly in the vanilla config camp. Neovim is very usable out of the box. Once you are invested in the interface (modal editing) then look to get 'fancy'. I think the big config approach just tries to make the editor an IDE. You don't most of that to try it out. Start simple.

ivanjermakov 3y ago

I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro. I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim https://github.com/nvim-lua/kickstart.nvim