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

vim-plug's "PlugInstall" not an editor command #3729

Closed
esn89 opened this issue Nov 23, 2015 · 11 comments
Closed

vim-plug's "PlugInstall" not an editor command #3729

esn89 opened this issue Nov 23, 2015 · 11 comments
Labels
closed:question issues that are closed as usage questions

Comments

@esn89
Copy link

esn89 commented Nov 23, 2015

I honestly am not sure whether to post this on vim-plug or here. So apologies in advance.

So right now, I just placed plug.vim in ~/.config/autoload and tried to run :PlugInstall from nvim and the "this is not an editor command" keeps poppin' up.

I have had success with vim-plug in the past on my older machines with neovim, so that is what prompted me to post here. Anyone else have the same problem?

@noahfrederick
Copy link
Contributor

~/.config/autoload

You are missing the nvim directory in that path: ~/.config/nvim/autoload/.

@esn89
Copy link
Author

esn89 commented Nov 23, 2015

hmm, i just tried it with the autoload dir and that didn't seem to work.

@fmoralesc
Copy link
Contributor

Did you initialize vim-plug in the init.vim file pointing it at the correct path? (:call plug#begin('~/.config/nvim')) The command only gets created then.

@noahfrederick
Copy link
Contributor

@esn89 In any case, this is almost certainly user error. You should refer to vim-plug's usage instructions.

Note that the :PlugInstall command will not be available until the autoload script is sourced, which occurs when you source it manually, or more usually, call one of the autoloaded functions, such as plug#begin() in your init.vim.

@ghost ghost closed this as completed Nov 23, 2015
@justinmk justinmk added the usage label Nov 27, 2015
@upgradeQ
Copy link

Also if someone like me stuck with no commands on neovim at all , it's because new Plug manager using different syntax , i hope it will save someones time Plug 'scrooloose/nerdtree', { 'on': 'NERDTreeToggle' }

@danschumann
Copy link

danschumann commented May 28, 2020

Make sure git is installed if you use the auto-install script.

@slalbertojesus
Copy link

If you are on manjaro, make sure to edit the .vimrc in this location:
/home/yourusername/.vim/vimrc

@justinmk justinmk added the closed:question issues that are closed as usage questions label Aug 30, 2020
@darklaser28
Copy link

Did you initialize vim-plug in the init.vim file pointing it at the correct path? (:call plug#begin('~/.config/nvim')) The command only gets created then.

Why don't I have the nvim folder in my .config file ?

@abd96
Copy link

abd96 commented Mar 12, 2021

Did you initialize vim-plug in the init.vim file pointing it at the correct path? (:call plug#begin('~/.config/nvim')) The command only gets created then.

Why don't I have the nvim folder in my .config file ?

You may create it yourself!

@missing-atabey
Copy link

missing-atabey commented Jun 24, 2021

Did you initialize vim-plug in the init.vim file pointing it at the correct path? (:call plug#begin('~/.config/nvim')) The command only gets created then.

Also, for anyone else that ends up dealing with this, (since I had this issue) if you make the init.vim file, make sure that it is ".vim" format when its first created. I attempted to create a formatless file, and a txt file with the lines needed inside so that I could then add the ".vim", and it failed both times because the data wasn't formatted properly as a result of the change in file extension.

@ronnycoding
Copy link

run :checkhealth that works for me to figure out what I've missed on my computer

@neovim neovim locked as resolved and limited conversation to collaborators Jul 11, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
closed:question issues that are closed as usage questions
Projects
None yet
Development

No branches or pull requests