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

faq: using SpaceVim without overwrite vimrc #1848

Merged
merged 1 commit into from Jun 19, 2018
Merged

faq: using SpaceVim without overwrite vimrc #1848

merged 1 commit into from Jun 19, 2018

Conversation

wsdjeg
Copy link
Member

@wsdjeg wsdjeg commented Jun 19, 2018

close #1844

@ghost ghost assigned wsdjeg Jun 19, 2018
@ghost ghost added the WIP Work In Progress label Jun 19, 2018
@codecov
Copy link

codecov bot commented Jun 19, 2018

Codecov Report

Merging #1848 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1848   +/-   ##
=======================================
  Coverage   26.28%   26.28%           
=======================================
  Files         253      253           
  Lines       12571    12571           
=======================================
  Hits         3304     3304           
  Misses       9267     9267

@bluddy
Copy link

bluddy commented Jun 19, 2018

I think this is good, but perhaps this could also be the default behavior, both for vim and neovim? As a distribution, you don't want to overwrite the tools you're using -- they have their own 'distribution'.

@wsdjeg
Copy link
Member Author

wsdjeg commented Jun 19, 2018

@bluddy, sorry, I can not make this behavior default, It is same behavior as spacemacs.

@wsdjeg wsdjeg merged commit 952f6b6 into SpaceVim:master Jun 19, 2018
@ghost ghost removed the WIP Work In Progress label Jun 19, 2018
@wsdjeg wsdjeg deleted the faq branch June 19, 2018 13:50
@bluddy
Copy link

bluddy commented Jun 19, 2018

But why do you need to be constrained by what spacemacs does?

@wsdjeg
Copy link
Member Author

wsdjeg commented Jun 19, 2018

@bluddy ok, if we make this behavior default, It will break many things, when using gvim, you can not load SpaceVim, gvim do not using alias.

This is just a vim config, it do not contains a exetable file, if we include vim into this repo, I would like to use new path instead of ~/.vim.

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