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

Helptags not getting loaded #31

Closed
jerodsanto opened this Issue May 12, 2011 · 8 comments

Comments

Projects
None yet
2 participants
@jerodsanto
Copy link

jerodsanto commented May 12, 2011

I've just tried switching from pathogen to vundle and the only thing that is lacking is autoloading the helptags for my installed plugins. I followed the readme as closely as possible, but for some reason they don't get set up properly.

The only thing non-standard about my install is that my configs don't actually exist in ~/.vim. Instead, they are in ~/src/dotfiles/vim and ~/.vim is a symlink to this directory. Could this perhaps be related?

It is also noteworthy that when I run the command myself, even using the symlink, it works, eg:

:helptags ~/vim/bundle/vim-rails/doc
@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented May 12, 2011

Hey sant0sk1!
Hm, interesting...
What does :BundleDocs say?

@jerodsanto

This comment has been minimized.

Copy link
Author

jerodsanto commented May 12, 2011

:BundleDocs said everything was all good, so I removed one of my plugins, ran :BundleInstall again, and sure enough the help was generated.

I think my problem was related to my vimrc trying to use a function from the fugitive plugin when it wasn't yet available, which messed up the :BundleInstall call or something. All is well now and I don't think it requires any changes on your end.

Thanks for the quick response and for the (so far) awesome plugin manager!

@jerodsanto jerodsanto closed this May 12, 2011

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented May 12, 2011

Well, that's a sign of Chicken & Egg problem...(
Do you find this a serious issue?

@jerodsanto

This comment has been minimized.

Copy link
Author

jerodsanto commented May 12, 2011

It's definitely an issue for me when setting up vim on a new machine, but I look at it more as a problem with my vimrc than with vundle itself.

I asked this question on SO to try and fix it. Perhaps you might have an idea of a workaround?

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented May 12, 2011

Instead of going with conditionals I can think about this approach:
Extract all Vundle related stuff into say bundles.vim.

then in your .vimrc:

source bundles.vim

Then initial installation will be just vim -u bundles.vim +BundleInstall +q

In this case you don't have to adapt your .vimrc and solve Chicken & Egg porblem.

Let me know how that works for you.

Thanks!

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented May 12, 2011

and to follow up - source bundles.vim has to be put somewhere before fugitive status call.

@jerodsanto

This comment has been minimized.

Copy link
Author

jerodsanto commented May 12, 2011

It works. Brilliant, thanks!

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented May 12, 2011

Awesome!
I'll add this to the FAQ section.
Thank you! )

0 pushed a commit to 0/vundle that referenced this issue May 30, 2011

closes VundleVim#31
- append slash to indicate directory, so expand ingnores wildignore
settings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.