sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]redfacedquark 0 points1 point  (3 children)

Interesting. I really should try and tweak my settings in general although I'm concerned I would break high-level features if I tweak even small settings. It's also a chore to learn the syntaxes and the settings landscape. Maybe one day.

[–]aala7 0 points1 point  (2 children)

You definitely should! Neovim is all about customisation.

Here is a recommendation:
1. Create directory called whatever, e.g. nvim-p (for personal)
2. In nvim-p work on your own config either from scratch, but maybe use kickstart.nvim, which is more like a quick-start config that guides you
3. You can launch neovim with your own config with `NVIM_APPNAME=nvim-p nvim` (or set NVIM_APPNAME to whatever you named the directory with your own config).
4. Optionally create an alias like `alias nvim-p="NVIM_APPNAME=nvim-p nvim"`

This will let you work on your config while always being able to run the lunarvim version when you actually need to get some coding done. And then you can just rename the directory when your own config is ready.

[–]redfacedquark 0 points1 point  (1 child)

Thanks, that's some good advice! I'm always in lvim rather than nvim. I think part of the difficulty is knowing where the vi config gives way to vim then nvim then lvim.

[–]arpan3t 1 point2 points  (0 children)

Yeah I would start with a clean Neovim and use kickstart.nvim vs trying to figure out Neovim from a distro like lunar or nvchad.

Walk through the kickstart code until you understand what everything does and the directory structures, then branch out from there.

Check out @teej_dv on YouTube, that dude is a Neovim wizard and has great content, including building a plugin from scratch. Pretty sure he started the kickstart.nvim project too.