init.lua (and that big pile of plugins).
So for the price of few weeks inconvenience I can stop spending time on text editor configuration and/or figuring out on how to install it.
@jarkko certainly an interesting choice. I'm grappling with this myself. On the one hand, VIM keybinds are ubiquitous and if I use an alternative editor or IDE such as Android Studio I lose the easy jump back and forth from neovim if I've relearnt helix keybinds.
@jarkko I keep finding interesting experiences people have around #vim . I started by using vim motions on VSCode, but found it slow (undo takes seconds). Then I tried nvim with the #LazyVim distribution but found it overwhelming. It went from a minimal black screen with text to a willy wonka UI with millions of moving pieces.
I'm giving another try to #neovim but adding as few plugins as possible and only one by one. What I meant with all this is: I agree, plugins are too much.
@almenal99 @jarkko I think what you're doing now is right. IMO everyone should start with a stock insurance and begin setting up your keybindings and options the way you want. From there, only reach for plugins when you REALLY want a new functionality. I think it's important also to make tweaks as you go. I see so many people kill full days on tweaking their config. However i think it's better to just keep your nvim config file open and hack on interleaved with your day job.