cheovim VS NvChad

From what I understand -u just sets the init.vim/init.lua, and does not set the config path internally to that location. The config would still point to the default configuration folder (~/.config/nvim in most cases). In the normal case this would lead to neovim not starting up properly due to not finding the rest of the config files (files that are require-ed). In a worse case it finds those names in the default config and you wonder why your new config is not working. To make it work properly, you would have to do some symlink hacks to mock different isolated profiles. This plugin was written to do exactly this. But now it's no longer needed since $NVIM_APPNAME allows different appnames (instead of multiplexing multiple configs over one config folder via symlinks).

I tried cheovim but like others in the issues, wasn't able to get anything to work unfortunately. So any help would be much appreciated.

This is probably what ur looking for: https://github.com/NTBBloodbath/cheovim

I usually use https://github.com/NTBBloodbath/cheovim to manage multiple configurations

One possible choice is https://github.com/NTBBloodbath/cheovim as to reduce loading time and clutter between setups.

- config - colors

NvChad

This repo https://github.com/siduck76/NvChad ?

https://github.com/siduck76/NvChad . Its meant to be used as a base config , isnt a framework like spacevim etc.

repo

Seems like lots of people have their own lua folder under ~/.config/nvim that init.vim or init.lua gets info from. One example of this structure is here

But to be honest, configuring vim to your taste also takes a lot of time (but on the other side, you could use preconfigured nvim nightly which does a lot for you).