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

random files put into .vim #1

Closed
rygwdn opened this issue Dec 4, 2010 · 3 comments
Closed

random files put into .vim #1

rygwdn opened this issue Dec 4, 2010 · 3 comments
Labels

Comments

@rygwdn
Copy link
Contributor

rygwdn commented Dec 4, 2010

I think this is actually an issue with git somehow (or maybe the way it's supposed to work), but sometimes when Vundle updates a plugin, it puts the updated files directly into my ~/.vim directory rather than into the bundle's directory (eg. an updated file will appear in ~/.vim/plugin rather than ~/.vim/bundle/pluginname/plugin). It seems to stem from using '--git-dir=' to pull stuff in. I have a little patch in my fork of Vundle which seems to fix it for me. My change just 'cd's into the bundle's directory, then does 'git pull'.

@gmarik
Copy link
Contributor

gmarik commented Dec 4, 2010

Hey Hey! First issue is here, eh?! )
Can you try running
git --git-dir=~/.vim/bundle/<vim_plugin_name> pull
to see if git really neglects --git-dir option? I believe older git version do so. May I know your git version?
Also i've checked your fork, but due to merge the fix kind of dissolved in merge, can you please do rebase instead merge? Just to have clean patch.
Thanks for feedback!

@rygwdn
Copy link
Contributor Author

rygwdn commented Dec 4, 2010

It's definitely not an old version of git, I'm using 1.7.3.2 :). I just checked the git docs, and apparently it's doing exactly what it's supposed to! In order to do what the code is actually intending to do (at least with git 1.7.3.2) you need to use the --work-tree= option along with the --git-dir= option, or do it the way I did in my fork. I rebased my fork so that you can merge cleanly if you like!

@gmarik
Copy link
Contributor

gmarik commented Dec 4, 2010

Seems like there's no other way to set --work-tree except cd-ing into it in this case.
Patch applied. Thanks!

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

No branches or pull requests

2 participants