-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
E492: Not an editor command: PluginInstall #932
Comments
What this means is that vim is not picking up your vundle installation. This is atypical, but not unheard of. To make sure that I fully understand --- make sure that you have closed vim and fully restarted it after modifying your vimrc. Assuming that you have done this, have you verified that |
I have encountered the same problem. In my case I had |
I find the reason。the error is in this line "set rtp+=~/.vim/bundle/Vundle.vim" |
It is not necessary to be root to use vim or to use vundle. But I think you are confused, as |
Thanks!You are right。Now my question is how to source .vimrc after I change it 。If I use :Source in vim ,It becomes effective in this file。but if I open another file。I need to use :Source too 。I source it in the shell, it can not work。 |
@284794507 Assuming Vim is finding your If your .vimrc changes don't seem to be working when you start Vim, you might want to check the location of the .virmrc file that Vim is loading by typing
in Vim. |
Is your vim a tiny version? If so, see #944 |
if it's show in after type wrong command in CMP panel, then just press esc and then type again your command, that you want to run. I hope this is fine. |
I 、git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim
2、edit .vimrc
set shell=/bin/bash
"vundle
set nocompatible
filetype off
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
Plugin 'VundleVim/Vundle.vim'
call vundle#end()
filetype plugin indent on
3、run :PluginInstall in vim ,but show "E492: Not an editor command: PluginInstall"
Can you help me?
The text was updated successfully, but these errors were encountered: