You can try nvim -u NORC path/to/file, which will allow plugins but not load your configuration file. Or, you can go the other way, nvim --noplugin to load your configuration but not plugins. To be clear, these are not meant to be long term solutions, only a couple things to help figure out how to narrow your focus on the problem.
Running :lazy from within nvim will show you how long each plugin took to load.
(edit: I forgot you mentioned you were using LazyVim, so you definitely using lazy.nvim)
I moved from VSCode to Neovim a few months ago with Kickstart as my initial config, which is fairly basic distro compared to Lazy or AstroNvim. Iām slowly getting used to Vim motion and adding some plugins here and there.
But sometimes Iām wondering if I should have picked up a more ācompleteā distro to smooth the learning curve, on the other hand, this choice should pay me back on the long run.
I started with Vim, then jumped ship to NeoVim about a year ago. My ~/.vimrc has become an ungodly mess of Vimscript, some Lua, and a bunch of shortcuts/mappings that make my life easier.
I tried switching to (Neo)Vim during the last almost 15 years several times and always failed. But this week it looks like is my first one when I am successfully using it almost exclusively.
Usually books focus on movements, text manipulation etc., but what I was missing was the real world scenarios like navigating files, projects, testing, debugging etc. This book address that pretty well. Highly recommended.
Ya, I used Janus for a short time years ago. I copied and adapted what I liked from it. Same as sentiments above.
Another great way to learn Vim is to read peoplesā vimrcs. I have read a lot of them over the years, I also read a lot of ones that arenāt necessarily āgoodā but due to the highly configurable nature of Vim, people get all sorts of unique ideas and I donāt think Iāve ever not learned anything from reading them. Tangentially, this is the reason I really appreciate when peopleās core config is in one big vimrc instead of being broken up. Lots of vimrcs read nicely from top to bottom.
Full agree here. I am aging and I am also still working on health so I have to be very wise with my energy expenditures and I have to prioritize my pursuits very aggressively. And I actually envy everyone around here for having the time, the energy and the desire to tinker with their editors. Ever since I landed on AstroNvim I had to customize it 3-4 times, took 10 minutes each time (actually super low-friction, much better than I expected) and I still rolled my eyes so hard that I was actually in danger of finally finding a brain in my head.
Since then I am super happy with it. Sure some bigger files and projects make it lag, it annoys me but it happens rarely enough for me to not care enough.
Huge props to @jswanner and the others for making me aware of nvim -u $stuff though! I absolutely will reach for it every now and then.
Oh damn, this is fantastic!
I didnāt know about it!
I went with LazyVim as well after a few attempts of setting up an environment I wanted and there was always something I missed or didnāt know how to do (skill issue 100%).
I used to use Vim a lot in the 2010s when I was working a lot in RoR but abandoned it for VSCode.
I had a couple weeks off during XMAS/New Year and fell down a rabbit hole setting up a new MBP and getting dotfiles setup. I ended up falling back in love with Vim through Neovim. I started out just tinkering with my own configs but quickly realized that the vast majority of my plugins were coming from Folke so I decided to give LazyVim a try. Absolutely love it. Out of the box itās configured very nicely. If youāre into the IDE feel youāll love LazyVim. I did end up disabling a few things that I felt took away from the āvim wayā like Bufferline, etc. but now I feel like itās perfect.
If I were (and I probably will down the road) go back to just rolling my own, Iād probably look into Kickstarter since itās mostly a barebones setup and more of a way to help you configure your own.
I personally hate this customization part too, or better said the lack of documentation and tutorials for beginners, itās like everyone knows how to do it already and you are coming late to the party.
Iāve personally switched from VSCode about half a year ago to NvChad first, then for some reason that I donāt remember anymore to AstroVim.
Overall I like it, especially since the only things I need when writing elixir is code highlighting and the language server, however I still cannot get used to things I used to do easily with a mouse, like copying multi-line text.