Don't touch the default nvim installation; use a seperate config directory.
2brownc opened this issue · comments
Brown commented
Currently recommended installation method makes CosmicNvim take over the nvim
command.
Use cvim
instead of taking over nvim
. It's better if the default nvim installtion is left as it is while CosmicVim has it's own runtime, config and cache directories.
Lunar Vim does exactly this. So even when CosmicVim is installed it runs with no issue. Example script for Lunar Vim which is invoked by lvim
:
#!/bin/sh
export LUNARVIM_RUNTIME_DIR="${LUNARVIM_RUNTIME_DIR:-"~/.local/share/lunarvim"}"
export LUNARVIM_CONFIG_DIR="${LUNARVIM_CONFIG_DIR:-"~/.config/lvim"}"
export LUNARVIM_CACHE_DIR="${LUNARVIM_CACHE_DIR:-"~/.cache/lvim"}"
exec nvim -u "$LUNARVIM_RUNTIME_DIR/lvim/init.lua" "$@"
Matthew Leong commented
This is on my radar now 👍