Open Henrai opened 2 years ago
had the same problem but later found the solution. check this out
Did you follow this instruction to install vim-plug?
Did you follow this instruction to install vim-plug?
Yes. But it has a little bug with vim 8+ and I found a possible solution
it has a little bug
There is no bug. If you put plug.vim file in the right autoload
directory, Vim will automatically load it when you run plug#begin
, and that's the whole point of autoload
. No manual sourcing is required.
I use vim on windows 10 and vim 9’.0 and I usually receive and error of function plug#begin not defined or something similar to that. And it caused some plugins not to function properly. I had to tweak my plug.vim to fix this.
Sent from my iPhone
On 27 Aug 2022, at 02:57, Junegunn Choi @.***> wrote:
it has a little bug
There is no bug. If you put plug.vim file in the right autoload directory, Vim will automatically load it when you run plug#begin, and that's the whole point of autoload. No manual sourcing is required.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
I needed to set
set runtimepath+=~/.vim
in my vimrc before plug#begin
because the autoload folder was not loaded
@azak-azkaran thanks, this worked for me.
I get this when set up the vim plugin :
And the result for :scriptname is this:
It seems that the vim-plugin is not loaded at all. I apply
chmod 777
to both .vim and .vim/autoload folder. Do we have any suggestions to manually load the plugin?Thanks!