kickstart.nvim

Curious why you went back to lazy.nvim? I had to write some stuff to get some kind of lazy loading (now have "immediate", "vim.schedule", and "VimEnter + vim.schedule" lazy modes), plugin specs / setup functions are colocated, and using vim.packs unused `data` for config merging and it works well enough. Also, your treesitter auto install makes a common mistake: vim file type and treesitter grammar names don't match up. IE a .tsx file has a vim filetype of `typescriptreact` while the treesitter parser is named "tsx". You'll need something like this https://github.com/nvim-lua/kickstart.nvim/blob/cfdc17be3ae1..., and there's still the note that the `vim.treesitter.language.get_lang` call isn't really doing anything, since that function returns whatever is passed in if no parser matching the name has been registered. So that check is moot.

The bloat of the neovim distributions are real and what I would suggest for anyone who is a long time vim user is to check out kickstart. https://github.com/nvim-lua/kickstart.nvim , specifically the modular fork https://github.com/dam9000/kickstart-modular.nvim which will give you a great (minimal) starting point

I tried LazyVim a couple of times, but felt that I would rather go back to a simpler nvim setup, and then build it up myself and learn as I go. I have stuck and enjoyed kickstart.nvim: https://github.com/nvim-lua/kickstart.nvim It has been my starting point, and I have gradually been adding new plugins and reconfiguring existing ones.

https://github.com/nvim-lua/kickstart.nvim single file config in lua with the essentials. Some of the article still rings true though.

I believe that the Neovim Kickstart project gives you Telescope as the fuzzy finder. (The YouTube video by TJ is linked in the README.) https://github.com/nvim-lua/kickstart.nvim

Similarly, I found the kickstart.nvim immensely helpful as a jumping off point. https://github.com/nvim-lua/kickstart.nvim

For casual users like me, I find Kickstart (https://github.com/nvim-lua/kickstart.nvim) a good and sensible default that's not too opinionated.

I usually recommend new users to check out Kickstart. It contains a set of plugins and nice to haves so you don't have to discover them your self. All plugins are in one file + has a lot of comments to help you get started. ref: https://github.com/nvim-lua/kickstart.nvim

I recently started with Kickstart paired with this video, it's really easy and beginner friendly. https://github.com/nvim-lua/kickstart.nvim https://www.youtube.com/watch?v=m8C0Cq9Uv9o

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

kickstart.nvim [1] is the best way to get started if you want to understand how things are configured rather than using someone else's config. It's a single file and you can pretty easily use it as a starting point for your own config. And it comes with the which-key.nvim [2] plugin that helps you learn vim motions. [1]: https://github.com/nvim-lua/kickstart.nvim [2]: https://github.com/folke/which-key.nvim

I spend a lot time inside vim/neovim on daily basis. I do have vscode open as well but it's mostly for referencing or file exploration on repos I'm not familiar with. Building a mental and muscle memory is tough but it requires grinding. You have to put in the time! It took me months! My biggest mistake was starting and playing around with configurations and plugins for days/weeks and constantly having a broken environment! Configuration hell is the worst path to get into neovim! Start with the starter kit but avoid going into installing 10s of plugins, custom key-mappings and themes until you have learned the fundamental of motions, navigations and editing. Starter kit: https://github.com/nvim-lua/kickstart.nvim