Testing neovim again

I have been a happy Helix user for some time by now. However, I like to come back to Neovim from time to time, to see if I can change the configuration in such way that I won’t have random nightmares about managing its init.lua file. Call it tinkering, it is a fun thing to do and there is nothing to lose, since I already have a working solution anyway.

This time, I checked if all I need works without lazy.nvim and with the default plugin manager. As it turned out - it doesn’t. I spent several hours trying to get any rainbow csv plugin to work and render csv files properly in a rainbow format, but failed every time.

So I went back to lazy.nvim. It is something I am familiar with anyway and it has a far better documented use cases across the internet. I managed to squeeze everything into it, while maintaining a somewhat decent readability of the file. Still, I am no developer, I use these editors as my text processors, mainly for markdown. My whole note-taking process is tied to them (to Helix at this point) and so the configuration gets a bit nuanced when it comes to text processing.

So far, I have a feeling I managed to build my best Neovim configuration ever. It only threw three errors after the initial load, and I managed to fix them without creating new ones. I know people tend to say, that lua is great, but no. The toml config file for Helix is just so much simpler. Anyway, one has to sacrifice something to gain another thing.

With Neovim I get a better markdown support. That is the truth. I also get a full rainbow csv support, something I can only emulate with the correct theme in Helix.

I will test my current Neovim setup for a few weeks to see, if it can replace Helix or not. So far so good.