Does this bug happen when you install plugin without vim-polyglot?
(not really applicable since it's vim's runtime files, but it does not happen without vim-polyglot)
Describe the bug:
Polyglot recently started breaking vimscript highlighting for me on vanilla vim. It looks like it changed with the fix for #578, where the vimscript files were swapped for neovim's. These don't seem to work with regular vim, causing unhighlighted command names, and highlighting most function calls in command definitions as errors.
I use Vim8 packages, without a wrapper, as an opt package, that I manually load before setting filetype and syntax.
To Reproduce:
Grab this minimal self-installing vimrc (or just don't load polyglot some other way)
" vim: ft=vim
call system('mkdir -p '.$HOME.'/pack/plugins/opt')
if empty(glob('~/.vim/pack/plugins/opt/polyglot'))
call system('git clone https://github.com/sheerun/vim-polyglot ~/.vim/pack/plugins/opt/polyglot')
end
if $USE_POLYGLOT == "yes"
packadd polyglot
end
filetype plugin indent on
syntax on
command! Foo call split(expand('%'), '/')
augroup edcon
autocmd!
autocmd FileType special echo expand(':e')
augroup END
Running two vim instances, the one on the left with just vim ~/.vimrc, the other one with USE_POLYGLOT=yes vim ~/.vimrc gives:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4
