Skip to content

Custom vimrc could use more exposure in documentation #122

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

Open
vuktw opened this issue Mar 1, 2025 · 0 comments
Open

Custom vimrc could use more exposure in documentation #122

vuktw opened this issue Mar 1, 2025 · 0 comments

Comments

@vuktw
Copy link

vuktw commented Mar 1, 2025

Searching the README for vimrc returns no results.

Reading the source code ~/.vim-anywhere/bin/run shows that vim-anywhere honors $HOME/.gvimrc.min and $HOME/.vimrc.min. Won't hurt mentioning it explicitly in the README.

As for custom vimrc just for vim-anywhere, vimrc in home directory is quite a relic. Vim moved from ~/.vimrc to ~/.vim/vimrc long ago, for the sake of decluttering home directory from dotfiles. From this perspective, perhaps it would make sense to bundle .gvimrc.min and .vimrc.min (and of course mention that in the README, as suggested above) straight into the repository and have the run script look for them in $HOME/.vim-anywhere instead of $HOME?

Having a full ~/vim-anywhere/vimrc directory a la ~/vimrc would be even better, since it would allow to bundle plugins just for it.

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

1 participant