New answers tagged

3

A general recommendation when debugging an issue is to start with -u NONE, which skips all initialization. If you just want to start vim without plugins and with a custom .vimrc file start vim with the following command: vim --noplugin -u <test_vimrc_file> <your_file_name> then issue the command :packadd <package_name> to load the plugin ...


0

Inside my vimrc I have a line that loads my plugins like this source ~/.vim/rc/bundles.vim Then inside my bundles.vim I do the following: call plug#begin('~/.vim/bundle') Plug 'foo/vim-someplugin' source ~/.vim/rc/plugins/someplugin.vim call plug#end() if you don't want to use hard coded paths I recommend something like this execute 'source' ...


2

Try this: set rtp-=~/.vim set rtp-=~/.vim/after set rtp^=/path/to/some-plugin set rtp+=/path/to/some-plugin/after set vif=NONE filetype plugin indent on syntax enable Write the code in a file, e.g. /tmp/vimrc, then start Vim with this shell command: vim -Nu /tmp/vimrc The -u argument specifies the path to a custom vimrc, while the -N argument resets '...


1

I cleaned out the installation and pulled the zip of vim-plug and extracted it into the autoload folder in vim82. Before I used the powershell solution. After that I made a custom plugin folder and gave it read/write permission. Now it seems to work. Unsure what the issue was but these ae the things that I changed. Also I should have mentioned that I am ...


0

:PluginInstall is the install command for Vundle. If it does not work Vundle is not installed correctly. Installation Instructions


1

Plug-in managers are largely interoperable in Vim, all modern plug-in managers work by updating 'runtimepath' to include the root of the plug-in in the list of paths, which is how Pathogen works (you could call Pathogen the "grandfather" of plug-in managers.) In your specific case, you are trying to install coc.nvim using Vundle. As you reported in issue #...


6

It allows the user to disable a specific plugin. See :h use-cpo-save, and search for NOT LOADING: NOT LOADING It's possible that a user doesn't always want to load this plugin. Or the system administrator has dropped it in the system-wide plugin directory, but a user has his own plugin he wants to use. Then the user must have a chance to ...


Top 50 recent answers are included