vundlevim / vundle.vim Goto Github PK

so we don't need to do it manually....

If I update plugins then display every plugin's new features just like in vim.org scripts, it will let user knows what you can do now.
Or is there some other way to view this info but I do not know ? If it is, I think combine it into vundle function is awesome.

Vundle does not seem to handle local repositories. If e.g. I add "Bundle 'file:///builds/vim-smart-statusline'" to vimrc and do a :BundleInstall it reports sucessfull installation but I only get an empty "file://builds" directorye inside ~/.vim/bundle.

Vundle currently formats its commands for cmd.exe if has('win32') || has('win64')). But this assumes win32 and win64 users have their shell set to cmd.exe. If bash.exe is used, vundle's commands fail because their syntax is wrong.

FYI: I use cygwin's bash for my shell and use the win32 version of gvim. (I don't use the cygwin X version of gvim because I don't want the overhead of running an X Server.)

The workaround is:

1. Add this to my .vimrc:
   set shell=$COMSPEC "This expands to the correct path to cmd.exe which vundle assumes for win32 and win64 users
2. And then add the msys version of git that works with cmd.exe.

However I'd rather use bash instead of cmd.exe for my shell. And I'd rather use the cygwin versions of git... (both personal preferences).

On my win32 version of gvim:
:echo &shell
returns: d:\cygwin\bin\bash.exe
Notice the path is formatted in the windows/dos format because it is the win32 version of gvim... and the folder for bash.exe could vary...

Proposed solution:
When has(win32) || has(win64), can you also test if shell contains 'bash.exe'? And if it's bash, format the command using the bash syntax rather than using the cmd.exe format...

(Related to this, I am wondering if further tests of the shell variable should be made? Is it cmd.exe? bash? bash.exe? csh? zsh? etc... And will commands work for each type of shell?)

Thanks

Hi. I'm attempting to fully switch from Pathogen, and I've noticed the following error when running :BundleInstall:

Error detected while processing function vundle#installer#install..vundle#instal
ler#helptags..53_helptags:
line    1:
E150: Not a directory: `=a:rtp.'/doc'`

I've followed the instructions closely, but something seems to be amiss. Any ideas?

Add a mechanism for loading bundles based on conditions, such as filetype detection?
For example, if I'm editing a Python file, I don't necessarily need to load all the Ruby plugins.

Feel free to close this issue if there's already a workaround I'm not aware of.

I installed vundle following README, such as:

$ git clone http://github.com/gmarik/vundle.git ~/.vim/bundle/vundle

and wrote .vimrc, such as:

set nocompatible               " be iMproved
filetype off                   " required!

set rtp+=~/.vim/bundle/vundle/
call vundle#rc()

Bundle 'rails.vim'
Bundle 'quickrun.vim'
Bundle 'Shougo/unite.vim'
Bundle 'Shougo/neocomplcache'

filetype plugin indent on     " required

when I executed :BundleClean, and answered y to the confirmation, vundle itself was removed, such as:

:!rm -rf '/home/s-kuroki/.vim/bundle/vundle'

I think vundle itself should not be removable by :BundleClean. or did I something in the wrong way?

Somebody asked me to try a specific revision of the scrooloose/NERDcommenter plugin.

I was looking for a way to do that with Vundle, but it seems I can't.

This might be a useful addition. I believe other people will use it too.

Thanks.

I am using my vim-slim plugin with vundle.

When I just use it with vundle, it ignores the ftdetect (It appears since the highlighting does not kick in) but when I manually run the commands out of the ftdetect file (IE :autocmd BufNewFile,BufRead *.slim set filetype=slim) and then open the slim files it loads the syntax highlighting.

Is there any reason that vundle would be ignoring the ftdetect directory?

In the tradition of many Vim plugins (for eg. Taglist, NERDTree, Fugitive), can you please add a global variable to indicate whether vundle is loaded? The objective is to make vimrc portable between different platforms/configurations.

Thanks.

Somehow I am unable to use vundle at all. I've followed 2 install steps: installed vundle via git clone and edited my .vimrc (see this gist).

Am I missing something or there's a bug in vundle?

P.S. Using Vim 7.3.

Hello, thanks for that great plugin, already switched from GetLatestVimScripts.

Main problem is that i can't add my .vim folder now to my git repo which handles all my dotfiles. It says there is problems with submodules.

# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#   modified:   bundle/neocomplcache (untracked content)
#   modified:   bundle/syntastic (untracked content)
#   deleted:    plugin/neocomplcache.vim
#   modified:   ../sh.d/S02_func
#
# Submodule changes to be committed:
#
# * .vim/bundle/neocomplcache 0000000...ffeacc0 (662):
#   > - Improved g:neocomplcache_disable_caching_file_path_pattern.
#
# * .vim/bundle/nerdcommenter 0000000...38630ff (184):
#   > add support for coldfusion
#
# * .vim/bundle/nerdtree 0000000...1dd345c (444):
#   > only set relativenumber for vim >= 7.3
#
# * .vim/bundle/supertab 0000000...21cd55b (63):
#   > fix <cr> after a <cr> completion selection when not chained w/ other mappings
#
# * .vim/bundle/syntastic 0000000...2c2f64f (157):
#   > tcl checker: fix a small typo
#
# * .vim/bundle/vim-fugitive 0000000...e047558 (147):
#   > Support :Gcommit on older Git versions
#

Uhh.. And why git sees folder as files?

#   new file:   bundle/neocomplcache
#   new file:   bundle/nerdcommenter
#   new file:   bundle/nerdtree
#   new file:   bundle/supertab
#   new file:   bundle/syntastic
#   new file:   bundle/vim-fugitive

For example, vim-latex puts the actual plugin directory in a "vimfiles" subdirectory, with other stuff in the repository root.

Is there some easy workaround to get these kinds of plugins to work with vundle, short of making another repo that only has that subdirectory?

I am trying to replace pathogen with vundle completely, but there are a couple of custom made ad-hoc plugins that I like to keep track in my main dotfiles repo. Once I got rid pathogen, these are not added to rtp, seems like vundle only adds whatever is passed to Bundle.

Could vundle handle this? Else any thoughts on a workaround?

Issuing BundleInstall! results in

fatal: destination path '/Users/nmk/.vim/bundle/vim-fugitive' already exists and is not an empty directory.

This happens with all packages, regardless of where they are installed from.

Any ideas if this is a setup issue on my end?

A couple examples would be a third-party plugin such as PeepOpen, or for testing plugins and color schemes.

An installer script (curl | bash, rvm style) (from #53)

In vundle#rc, use $HOME/vimfiles/bundle if its a windows OS, like the rest of the vim user files.

Executing BundleInstall! will update existing bundles.
On Windows it will execute the following command:

C:\Windows\system32\cmd.exe /c cd "C:\Users\<username>\.vim\bundle\nerdcommenter" && git pull

This call results in : fatal: Not a git repository (or any of the parent directories): .git
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cmd.mspx?mfr=true says:

You can use multiple commands separated by the command separator && for string, but you must enclose them in
quotation marks (for example, "command&&command&&command").

So the command to execute has to be:
C:\Windows\system32\cmd.exe /c "cd "C:\Users\<username>\.vim\bundle\nerdcommenter" && git pull"

Next problem: cd on Windows does not change drive. So when you are editing a file on drive D: and call BundleInstall! (with vim configuration on drive C:) cd does not work. You have to add the parameter /d for cd on Windows to change drive.

So the command to execute has to be:
C:\Windows\system32\cmd.exe /c "cd /d "C:\Users\<username>\.vim\bundle\nerdcommenter" && git pull"

This change in installer.vim works for me on Windows 7 Professional 64bit:

func! s:sync(bang, bundle) abort
    let git_dir = expand(a:bundle.path().'/.git/')
    if isdirectory(git_dir)
        if !(a:bang) | return 0 | endif
        let l:quotes = (has('win32') || has('win64')) ? '"' : ''
        let l:drive = (has('win32') || has('win64')) ? '/d ' : ''
        let cmd = l:quotes.'cd '.l:drive.shellescape(a:bundle.path()).' && git pull'.l:quotes
    else
        let cmd = 'git clone '.a:bundle.uri.' '.shellescape(a:bundle.path())
    endif
    silent exec '!'.cmd
    return 1
endf

(Note the two new variables l:quotes and l:drive.)
Could not test this on Linux or Mac.

Another fix is here: https://github.com/kien/vundle/commit/c014cd37a105f3d655b354cf196f4bce67c72132

Pulling latest head results in a slew of the error "Argument required: Bundle" being spat out upon processing my bundle config file. Moving back to the commit (06088de) prior to "Allow comments after Bundle declarations" (d840b24) causes the error to cease.

Mac OS X 10.6
MacVim 7.3.53
Using https://github.com/edgecase/vim-config

If I fork a bundle and change my configuration to use my fork, neither :BundleInstall or :BundleInstall! will pick it up - I would guess Vundle is just doing git pull without bothering about remotes.

The workaround of course is to delete the existing clone (or manually change the remotes) but it would be better if Vundle handled it for us.

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.)

hlsearch is a global option

Lately I'm getting burned by installing Vim plugins at HEAD instead of a stable branch or tag version. It'd be nice to be able to lock onto a stable tag or branch to prevent this from happening. Is this a possibility?

For :Bundles and :BundleSearch, show the short description for listed bundles. That is, the second column in the table on vim-scripts.org. I often find I need to go to that site just to see what a bundle really does.

As I see it there are three possible formats for this.

Comment First

This is most similar to common formatting of source code. A down side is the need for extra whitespace.

" Vim Ex-command wrapper for Ruby Bundler
Bundle 'bundler'

" ku source: bundle
Bundle 'ku-bundle'

" Load a series of files easily
Bundle 'bundle'

Comment After

Feels more like a description as one might design it on a website; puts focus on the Bundle line. Also whitespace-heavy.

Bundle 'bundler'
" Vim Ex-command wrapper for Ruby Bundler

Bundle 'ku-bundle'
" ku source: bundle

Bundle 'bundle'
" Load a series of files easily

Comments Lined Up

This makes yanking include the description, for better or worse. Easier to scan. Doesn't require more whitespace than without descriptions. Unlikely to work well with long bundle names.

Bundle 'bundler'    " Vim Ex-command wrapper for Ruby Bundler
Bundle 'ku-bundle'  " ku source: bundle
Bundle 'bundle'     " Load a series of files easily

doesnt work when used with Bundle "molokai"

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'.

Just tried following the instructions on the README. But when I try :h vundle I get:

E149: Sorry, no help for vundle

Any idea what I might be doing wrong?

Hey there -

I'm just getting started with Vundle and loving it except for one issue i've run into - it seems whenever I run the ":BundleClean" command, vundle tries to uninstall itself. I'm running macVim and have ported from a Janus (https://github.com/carlhuda/janus) installation.

Any ideas?

thanks in advance!
-matt

I'm getting the following after I issue: vim -u initrc +BundleInstall +q

Error detected while processing /home/itaine/.vim/bundle/vundle/autoload/vundle.vim:
line 8:
E10: \ should be followed by /, ? or &
line 11:
E10: \ should be followed by /, ? or &
line 14:
E10: \ should be followed by /, ? or &
line 17:
E10: \ should be followed by /, ? or &
line 20:
E10: \ should be followed by /, ? or &
line 24:
E10: \ should be followed by /, ? or &

When an error is encountered in helptags, vundle should continue to process the rest of the plugins. Currently it stops, meaning that a help error in one plugin can leave some or all of the other plugins without usable help.

It's not clear which bundles are up-to-date and which are being updated.

Here's an example of :BundleInstall!

Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
remote: Counting objects: 8, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 5 (delta 2), reused 3 (delta 0)
Unpacking objects: 100% (5/5), done.
From https://github.com/scrooloose/nerdcommenter
   5a93714..b28e7be  master     -> origin/master
Updating 5a93714..b28e7be
Fast-forward
 plugin/NERD_commenter.vim |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
Already up-to-date.
Already up-to-date.
remote: Counting objects: 48, done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 39 (delta 18), reused 30 (delta 9)
Unpacking objects: 100% (39/39), done.
From https://github.com/majutsushi/tagbar
   762df7a..b8b0e92  gh-pages   -> origin/gh-pages
   5da1632..3b389ae  master     -> origin/master
Updating 5da1632..3b389ae
Fast-forward
 autoload/tagbar.vim | 2840 +++++++++++++++++++++++++++++++++++++++++++++++++++
 doc/tagbar.txt      |   41 +-
 plugin/tagbar.vim   | 2802 +--------------------------------------------------
 syntax/tagbar.vim   |    6 +-
 4 files changed, 2883 insertions(+), 2806 deletions(-)
 create mode 100644 autoload/tagbar.vim
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.

Know what I mean? :)

I use different colorschemes for Vim and GVim so :BundleInstall will make GVim use the Vim colorscheme. Not a biggie, solved by restarting GVim or a simple :so $MYGVIMRC but still not optimal.

Thanks for a very useful tool! :)

When using a color scheme installed via vundle it doesn't seems to work. The actual scheme is located in:
~/.vim/bundle/vim-railscasts-theme/colors/railscasts.vim

While .vimrc says: colorscheme railscasts (also, see this gist).

I can provide any additional info if required.

it will be good to provide the progress of BundleInstall

This is a feature request.

It'd would be convenient to have a user settable global variable that controlled whether the git clone command that is execute to download plugins makes a full clone or the original repo or a shallow copy.

Ideally, this shallow copy would include only the latest revision (--depth 1)

It would be even nicer if whatever the global setting is, it could be overridden on a per bundle basis.

Shallow clones can speed up download time significantly if there are many plugins installed, specially when repos have many revisions.

The documentation says that in your .vimrc you must invoke

filetype off

and later

filetype plugin indent on

Will vundle still work if you only do filetype plugin on? If so, I’d be willing to update the documentation; if not, could its behavior be changed to work without this? I don’t love the automatic indentation and would rather have it off, if possible.

I wrote a small function to handle this. I wonder if I should send a pull request?

Diff: https://github.com/kien/vundle/commit/9bc49f829429cef8ab0e42c99450051ed8e2b91f

Hey guys,
I get this issue while using :BundleInstall. I should note that I'm changing the default bundle directory via call vundle#rc('/cygwinpath/')

Here's the error

Error detected while processing function vundle#installer#install..19_install..19_sync:
line 14:
E34: No previous command
Error detected while processing function vundle#installer#install..19_install:
line 4:
E714: List required
Error detected while processing function vundle#installer#install:
line 6:
E714: List required

My vimrc is as follows.

set nocompatible
set rtp+=/cygdrive/d/Dropbox/My\ Dropbox/!config/vim/bundle/vundle/
filetype off
call vundle#rc('/cygdrive/d/dropbox/my\ dropbox/!config/vim/bundle/')
Bundle 'gmarik/vundle'
Bundle 'Solarized'
filetype indent on

You can see that I've located my vim files in my Dropbox. Everything loads up fine. I've tried :Bundles foo to find packages and it works. I just can't get past the above error when I run :BundlesInstall

I've just instaled vundle for my vim 7.2.
Everything seems to be ok, except when I tried "BundleClean ack.vim", it did absolutely nothing.
The command just completed without any message.

Vundle is supposed to work in 7.2, isn't it?

I've been using vim-addon-manager, which does more or less what this addon seems to do. I've not used vundle yet, so I'm not sure how similar the two addons are, but VAM does provide the same core functionality of allowing addons to be installed and enabled from within vim itself. VAM is a bit sprawling, partly because it also does the work of vim-scripts.org itself, allowing addons to be pulled in directly from vim.org or from git, SVN, hg, etc. repos. So it's nice to see this more concise addon being made available as a potential replacement.

One thing that VAM provides that I don't see in vundle is the ability to declare addon dependencies. Each addon can have a file called ${ADDON_NAME}-addon-info.txt in the root of its directory structure. This text file is in vim-compatible JSON format and allows various metadata, including dependencies on other addons, to be declared. To me, this is a must-have feature, since it provides a way to modularize complex VimL code into libraries, allowing more complex functionality to be shared among addons and reducing code duplication and memory footprints.

Is there a possibility that this feature might be worked into vundle? If so, could a compatible metadata format be used?

BundleClean wants to delete all the bundles installed. It seems that there is a problem with forward/back slashes in 'path' comparison. Look at this function:

func! s:bundle.path()
  return join([g:bundle_dir, self.name], '/')
endf

On Windows, the resulting path is:

C:\foo\bar\bundles/teh_bundle

while globpath returns

C:\foo\bar\bundles\teh_bundle

(Note the last slash)

So, when they are compared in vundle#installer#clean function, they are treated as different bundles.

The solution that works for me:

func! s:bundle.path()
  let l:slash = (has('win32') || has('win64')) ? '\' : '/'
  return join([g:bundle_dir, self.name], l:slash)
endf

some scripts was not in the exact path they demanded.
e.g.
The css_color should be in "css_color/after/syntax/" ,
but it was in the "css_color/syntax/" folder.
that make it doesn't work

PS: will hg be supported?
projects that hold by google code could only be checked out by mercurial.

This is less of an "issue" and more of an idea. I noticed on autoload/vundle/installer.vim:48 you have a TODO about not reloading vimrc. And my coworker (trotter on github) had an interesting idea about putting the Bundle lines in their own file such that you could then have commands to manage them. For example you could run :BundleInstall tpope/vim-fugitive from within vim which would check out the bundle and append it to your "bundlerc" so it would get loaded next time.

Seems like it might kill two birds with one stone if you moved the actual bundle list into it's own file and loaded it during vundle#rc.

Thoughts?

just sayin

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

Hi!

There's something strange with the vividchalk.vim bundle.
I installed it and did "colors vividchalk", and it worked ok.
But in my next vim session (after I closed/opened the editor), "colors vividchalk"
resulted in "cannot find color scheme vividchalk" message.
After that, I did "BundleInstall vividchalk.vim", it said "no new bundless installed",
but "colorscheme vividchalk" worked again.

(btw, s/bundless/bundles/, eh?)

Hi.

I think there is a problem loading plugins with DOS formatting.

For example, add this bundle to your .vimrc and install it: Bundle "CSS3-Highlights"

Then, try to open a *.css file, and you will get the following errors:

Error detected while processing /Users/ory/Documents/dotfiles/vim/bundle/CSS3-Highlights/syntax/css.vim:

line    8: E492: Not an editor command: ^M
line   11: E15:  Invalid expression: !exists("main_syntax")^M
line  303: E488: Trailing characters
line  309: E171: Missing :endif

This happened on another plugin as well: Bundle "Better-CSS-Syntax-for-Vim"

I'm using both MacVim & Vim, OSX 10.6.6 Snow Leopard.

Thanks very much for your time! Your plugin is amazing!
Ory

Hello.

Related to bug #15, same problem again - i can't use vundle if i keep my .vim directory under git control.

Just found that article - http://boxysystems.com/index.php/nested-git-repo-gotchas/ - it describes problem related to .git inside .git.

Basically, if i checkout my .vim folder from git, i get bundles without .git directory and i can't update it - git says "fatal: directory already exists"

Is there any workaround?