Hi there, glad to see new users. I would recommend using LSP instead of Coc if your language is supported. A good starting point could be with Lsp-Zero plugin, it can be used with some dependencies and you can customize to your liking. A bit of a steep learning curve maybe, but the result is worth the effort. Also, using Packer for plugin management might be a good alternative, and learning lua in the process. I finally converted my vim config into Lua, I can send a link to my repo if you want to take some inspiration.
this post was submitted on 21 Jul 2023
5 points (100.0% liked)
Neovim
2508 readers
1 users here now
founded 2 years ago
MODERATORS
Welcome! I recommend checking out https://github.com/nvim-lua/kickstart.nvim. From their readme:
A starting point for Neovim that is:
- Small
- Single-file (with examples of moving to multi-file)
- Documented
- Modular
This repo is meant to be used by YOU to begin your Neovim journey; remove the things you don't use and add what you miss.
My current neovim config is basically this, plus a few plugins added / removed.
How familiar are you with vim? You've been using it with vscode for a while so I figure you're somewhat familiar with vim shortcuts? If you haven't already, you should run through vimtutor. The built in help is very good in vim, it's good to develop a habit of using :help and :helpgrep before googling. When in help pages you can use C-] to go to references in the documentation.
Some resources that I found useful when getting in to vim:
Articles: Oil and vinegar, Death by a thousand files
Talks: Let vim do the typing, How to do 90% of what plugins do with just vim
Speaking of plugins, tpope has an excellent repo of very good plugins that feel like they fit in very naturally with vim. I can especially recommend fugitive, commentary and surround