Home

Vundle Wiki

FAQ

Why am I asked for username/password?

This is an occurrence of an invalid repository name being used with Bundle, which then attempts to clone a nonexistent repo:

git clone http://github.com/gmarik/non_existin_repo
Cloning into non_existin_repo...
Username: 
Password: 
fatal: Authentication failed

My configuration is bundle-dependent,

so installing plugins for the first time in a fresh configuration produces errors. How can I fix that?

A: Fix your Chicken or Egg dilemma

How do I disable indentation set by plugins?

A: Use filetype plugin on instead of filetype plugin indent on.

With a default shell other than sh or bash

(e.g., fish), errors result when running BundleInstall!. Is there a way to fix this?

A: Vim will throw an error when running BundleInstall! if the default shell is not POSIX-compliant. Even if you manually switch to sh or bash from a different shell, the errors will continue if vim is not explicitly told to use sh or bash. The best way to rectify this is to: (1) add set shell=bash to your .vimrc, and (2) set the SHELL environment variable to sh or bash before running BundleInstall!. If using the fish shell, initial Vundle installation as well as updates can be performed by creating the following function at ~/.config/fish/functions/updatevim.fish and then running updatevim to install/update Vundle and its bundles:

function updatevim
    set SHELL (which sh)
    vim +BundleInstall! +BundleClean +qall
    set SHELL (which fish)
end

I am getting the following error:

Cloning into /root/zuo/.vim/bundle/The-NERD-tree...
error: SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing https://github.com/vim-scripts/The-NERD-tree.git/info/refs

A: Add let $GIT_SSL_NO_VERIFY = 'true' to your .vimrc.

It seems like Vundle cannot find the color scheme I just installed.

A: Make sure colorscheme my_awesome_colorscheme is called after the Bundle 'my_awesome_colorscheme' command. See #119 for details.

How do I make vundle install plugin to another path?

A: pass custom path as an argument, like : call vundle#rc("~/a/nother/path")

Vundle on Mac OS X

Why does vim exit with an error?

A: Using filetype off with stock OS X vim (located at /usr/bin/vim) causes vim to exit with a non-zero error code in completely valid cases. The workaround is to enable filetype before disabling it, like this:

    filetype on
    filetype off

    "... your configuration goes here

Vundle-for-Windows