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. #634

Closed
2brownc opened this issue Jun 13, 2022 · 3 comments · Fixed by #639
Closed

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

2brownc opened this issue Jun 13, 2022 · 3 comments · Fixed by #639
Labels
enhancement New feature or request

Comments

@2brownc
Copy link

2brownc commented Jun 13, 2022

Is your feature request related to a problem? Please describe.
Currently recommended installation method makes AstroNvim take over the nvim command.

Describe the solution you'd like
Use avim instead of taking over nvim. It's better if the default nvim installtion is left as it is while AstroVim has it's own runtime, config and cache directories.

Lunar Vim does exactly this. So even when AstroVim 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" "$@"

Additional context
A different config directory is useful because some guis Neovim require config files in nvim directory. So if AstroVim has a different directory it can be updates without any extra steps as in recopying the file afterwards.

@2brownc 2brownc added the enhancement New feature or request label Jun 13, 2022
@mehalter
Copy link
Member

This adds a layer of complexity to setting up AstroNvim for most users for a case I don't think is generally needed. I will definitely add this to the documentation though in the recipes section with detailed instructions on how to set this up and an example avim script that users can copy/paste and set up themselves. What do you think? As for the GUI compatibility, I think most users who use AstroNvim as well as a GUI based Neovim client want to use AstroNvim with their GUI client. Maybe we can add common GUI config files to our gitignore to help with this compatibility with the updater. Do you have any examples and I can add those files to not be tracked

@2brownc
Copy link
Author

2brownc commented Jun 13, 2022

I will definitely add this to the documentation though in the recipes section with detailed instructions on how to set this up and an example avim script that users can copy/paste and set up themselves.

That's great!

Maybe we can add common GUI config files to our gitignore to help with this compatibility with the updater. Do you have any examples and I can add those files to not be tracked.

Good idea!

I use Neovim-qt and it uses the file ginit.vim.

@mehalter
Copy link
Member

Awesome thanks, I'll take a look into this this upcoming week and check out some other GUI applications to get a decent list together. Thanks for the recommendation!

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

Successfully merging a pull request may close this issue.

2 participants