search

VundleVim / Vundle.vim

Vundle, the plug-in manager for Vim
http://github.com/VundleVim/Vundle.Vim
MIT License
23.89k stars 2.57k forks source link

:BundleInstall! hangs #60

Closed aherrmann closed 13 years ago

aherrmann commented 13 years ago

When typing :BundleInstall! in gvim it simply hangs. When typing it in vim it switches to the shell and prints Alread up-to-date. endlessly. When running vim '+BundleInstall!' the same happens. Pressing ^C brings me back inside vim where I can quit it. gvim on the other hand doesn't react anymore.

:BundleInstall without the bang works fine.

My setup is

call pathogen#runtime_append_all_bundles()
call pathogen#helptags()

set nocompatible
filetype off
set rtp+=$HOME/.vim/vundles/vundle
call vundle#rc($HOME . '/.vim/vundles')
Bundle 'gmarik/vundle'

where '$HOME/.vim' is a symlink to '.dotfiles/vim'. I'm still using pathogen for a few plugins in '.vim/bundle'. Vundles are installed to '.vim/vundles'.

Here's my full vimrc [https://github.com/aherrmann/dotfiles/blob/master/vim/vimrc]. (Sorry about the german comments, you can ignore them.)

0 commented 13 years ago

Do you wait for at least 37 "Already up-to-date." messages? Each of them should come from the git update of a single bundle.

If you do, in fact, see more of the messages than you have Bundle lines, try to add silent exec '!echo '.git_dir as the second line of s:sync in autoload/vundle/installer.vim. That should tell you to which bundle each output message corresponds.

aherrmann commented 13 years ago

Oops, I guess I was a little bit too impatient. Sorry. It prints 'Already up-to-date' 37 times indeed.

Why are these messages printed to the terminal and not inside vim? In gvim there is no message until :BundleInstall! is done. With vim there is that switch to the terminal.

gmarik commented 13 years ago

Hey! Interesting... I copied bundles you have and had no problems installing them with :BundleInstall!. There was an error

Error detected while processing /private/tmp/vundle_bundles/TaskList.vim/plugin/tasklist.vim:
line  369:
E227: mapping already exists for \t

but that's not something that would make it hang... Your config needs some more investigation i guess..)

aherrmann commented 13 years ago

Your config needs some more investigation i guess..)

Thanks. Feel free to copy anything you find useful...

Btw, I wrote a script to help me transfer the bundles from being managed by pathogen and git-submodules to being vundles. You'll find it here: https://github.com/aherrmann/dotfiles/blob/master/.gitscripts/submodule_to_vundle The script assumes that the current working directory is the git root dir, i.e. ~/.dotfiles in my case.

There are a few other scripts in that .gitscripts directory, but they were mostly used for submodule management.

gmarik commented 13 years ago

Nice! I think we could your script to help people migrate!)

gmarik commented 13 years ago

All the warnings are because pathogen and Vundle have overlapping functionality. You need one of them )

Also for some reasons I cannot reproduce issue you described: can't make it hang... Maybe Vim/OS matters in this case?

aherrmann commented 13 years ago

I think we could your script to help people migrate!)

Sure. I made a few modification. Adjust it to your repository layout by setting bundledir. submodule_to_vundle

All the warnings are because pathogen and Vundle have overlapping functionality. You need one of them )

Do you mean those Already up-to-date messages? That was solved by 0 here

Also for some reasons I cannot reproduce issue you described: can't make it hang...

That was me being too impatient. ;) So far I'm not having any visible collisions between pathogen and vundle.

Btw, in the README you write that setting filetype off is required. Why is that? It introduced some errors in filetype detection. vim-files were identified correctly as ft=vim, but shell scripts and python files were mistakenly taken for config files ft=conf.

I removed that line and it seems to work. Filetypes are detected correctly, plugins are loaded and no error messages appear.

gmarik commented 13 years ago

So far I'm not having any visible collisions between pathogen and vundle.

Well, my question is: why would you need both? As for filetype issue: having both may cause that...

Ok, looks like we have all issues dealt with, closing then!

Feel free to add migration script to Wiki! ) Thank you!

aherrmann commented 13 years ago

Well, my question is: why would you need both?

I still use pathogen for bundles that I modified or that I didn't find a git repository for when I installed them.

As for filetype issue: having both may cause that...

Maybe, but without the filetype off line I don't have any issues so far.

Ok, looks like we have all issues dealt with, closing then!

Yes, everything seems to work. Thanks.