3

So your question has already been asked in vim-plug's issue tracker, see #905. @raindev said this (I changed the link to the code to not use master in case the code changes in the future): I don't think that will work currently as each call to plug#begin resets Plug configuration (and not appends to it): https://github.com/junegunn/vim-plug/blob/...


3

A brief word on how vim-plug works... The main part of a plugin config is a path on GitHub. In your case dracula/vim refers to https://github.com/dracula/vim. What vim-plug needs to do, then, is download/install (using git) the plugin code from that address. But it doesn't happen automatically. It's up to you to run the command :PlugInstall. (And do so each ...


3

The effect you're seeing is due to the set nocompatible command resetting many other options, 'iskeyword' included. From :help 'nocompatible': This is a special kind of option, because when it's set or reset, other options are also changed as a side effect. NOTE: Setting or resetting this option can have a lot of unexpected effects: Mappings are interpreted ...


1

You can only call plug#begin() and plug#end() once, so no this will not work. You can define all your plug-ins from the same place (such as the vimrc file) and use a conditional to detect whether you're running NeoVim to load plug-ins you only want on NeoVim: call plug#begin('~/.vim/vim-plug-in') " Vim + NeoVim plug-ins if has('nvim') " NeoVim-...


1

In theory you could give the same path to both plugins managers so that they install the plugins in the same directory: vim-plug call plug#begin('/path/to/your/plugins') vundle call vundle#begin('/path/to/your/plugins') In theory you could use one of the managers to install your plugins (PlugInstall for vim-plug or PluginInstall for Vundle), this plugin ...


1

That's an interesting question! To my knowledge, there is no option to do so. I think it's better to let the user chose his own mapping to avoid collisions. This is the reason why some plugins use <Plug> for their features (see :help using-<Plug>). I am happy to see that you are keen on plugins (they are really useful), but I suggest you to not ...


1

filenameescape() is supposed to be the solution. And yet, I've cooked my own solution 2 decades ago and it's still working fine so far. function! lh#path#fix(pathname, ...) abort " Parameters {{{4 " Ignore the last slash or backslash character, if any let pathname = matchstr(a:pathname, '^.*[^/\\]') " Default value for the ...


1

Two solutions: On a current windows 10 machine that I have access to for work with a user account only, I was able to sucessfully install the standard vim version, named 'self-installing executeable' that is available here: https://ftp.nluug.nl/pub/vim/pc/gvim82.exe Administrator access was not required. This version comes with an autoload folder (unlike ...


Only top voted, non community-wiki answers of a minimum length are eligible