Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't touch the default nvim installation; use a seperate config directory. #78

Open
2brownc opened this issue Jun 28, 2022 · 1 comment

Comments

@2brownc
Copy link

2brownc commented Jun 28, 2022

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" "$@"
@mattleong
Copy link
Collaborator

This is on my radar now 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants