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

E492: Not an editor command: PluginInstall #932

Open
284794507 opened this issue May 12, 2020 · 8 comments
Open

E492: Not an editor command: PluginInstall #932

284794507 opened this issue May 12, 2020 · 8 comments

Comments

@284794507
Copy link

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?

@davidlowryduda
Copy link

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 .vim/ exists and is filled as you expect? Sometimes people forget which vimrc they are using. It might be a good idea to make sure that your vimrc is being sourced. (This is particularly relevant if you are a new user of neovim and forget that init.vim != .vimrc).

@cs91chris
Copy link

I have encountered the same problem. In my case I had export VIMINIT=":set nobackup noswapfile encoding=utf8 viminfo=" in my .bashrc, after remove it, vundle works.

@284794507
Copy link
Author

284794507 commented May 27, 2020

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 .vim/ exists and is filled as you expect? Sometimes people forget which vimrc they are using. It might be a good idea to make sure that your vimrc is being sourced. (This is particularly relevant if you are a new user of neovim and forget that init.vim != .vimrc).

I find the reason。the error is in this line "set rtp+=~/.vim/bundle/Vundle.vim"
I am not the root user ,so I need to use $HOME/.vim
but I can not source .vimrc。Is there another command to use without reboot system

@davidlowryduda
Copy link

It is not necessary to be root to use vim or to use vundle. But I think you are confused, as ~ in typical bash expands to the same directory as $HOME. And I don't understand what you are referring to when you mention a system reboot.

@284794507
Copy link
Author

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。

@ratfactor
Copy link

@284794507 Assuming Vim is finding your .vimrc file, it will be run when you first start Vim. Nothing will be lost when you open new files (assuming plugins or file type autocommands aren't interfering).

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

 :echo $MYVIMRC

in Vim.

@biaocy
Copy link

biaocy commented Nov 11, 2020

Is your vim a tiny version? If so, see #944

@hemant-rao
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants