28
submitted 1 year ago* (last edited 1 year ago) by onlinepersona@programming.dev to c/neovim@programming.dev

I thought switching from vim to neovim would be like switching from a nano+ to a VSCode CLI, but it's far from that. There are so many plugins and it's not as easy as declaring which plugins I want, having one dictionary/mapping/attribute set with keybindings, another with global preferences, and done.

Then there's something about language servers. The list on https://github.com/rockerBOO/awesome-neovim is daunting. I thought LSP support was built into nvim. Why are there so many LSP plugins? And what the hell is treesitter and why do I need it?

I copied some dude's config and suddenly Ctrl+P for completion didn't work like in VIM.

There's just so much unexplained jargon and abbreviations, that it feels like I have to read neovim code before even using it (ain't nobody got time for that). Is neovim actually the right tool to use to have an easy CLI IDE? Is there an easier command-line alternative that just lets me go "oh, this language isn't supported, let me open the package manager and install the $language-plugin", with "Goto Definition", debugging with breakpoints, code formatting, refactoring (rename variable/method/class, extract function, etc.) ? Maybe neovim just isn't the right tool for those without years of time.

Edit: Thanks for the suggestions everybody. Finally went with Lunarvim and it's been a joy!

you are viewing a single comment's thread
view the rest of the comments
[-] RayZ0rr@programming.dev 1 points 1 year ago

This here is also a good starting point for Neovim: https://github.com/nvim-lua/kickstart.nvim

this post was submitted on 23 Sep 2023
28 points (96.7% liked)

Neovim

2161 readers
3 users here now

founded 1 year ago
MODERATORS