-
Based on this comment, I would strongly suggest using lazy.nvim as your package manager. It will create a lazy-lock.json file whenever you update your plugins, so your config will allways be reproducible (as long as the github repos holding your plugins are still available). You could wait 10 years and keep using your neovim config as long as you don't change your Neovim version.
-
CodeRabbit
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.
-
https://github.com/nvim-lua/kickstart.nvim here's the kickstart as a place to begin.
-
-
NvChad
Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
Use a pre-build config such as Lazyvim or Nvchat. I haved used none of them, but used them as inspiration for setting up my new dotfiles.
-
-
https://github.com/williamboman/mason-lspconfig.nvim - Mason plugin to manage your LSP servers.
-
If you have questions about how to mix `vimscript` and `lua`, you are refer to my previous dot files, which are kind of dirty but it might be helpful : https://github.com/logeekal/dotfiles/tree/ansys-ubu
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
Use a pre-build config such as Lazyvim or Nvchat. I haved used none of them, but used them as inspiration for setting up my new dotfiles.
-
It took me around 2 days to do everything from scratch with Lazy. Here is my new config in case you are interested: https://github.com/logeekal/dot-files
-
you can try my neovim config: https://github.com/linrongbin16/lin.nvim