Open davidde opened 3 years ago
The language id used is viml
, not vim
. Does it work if you fix your file associations that way? If not then this is a vscode issue as this is the one that "recognizes" and activates the matching extension.
As I'm no VIM-expert: are those files common and listed in the VIM-docs?
Does not seem to work with viml
either. .vimrc
with leading dot is clearly more common, but I wouldn't say ~/.vim/vimrc
is uncommon.
nvimrc
probably is not required after all, since nvim uses ~/.config/nvim/init.vim
by default, and can source anything required from there.
This extension would be a lot more useful if it was capable of also recognizing
vimrc
andnvimrc
without the leading dot.Neither does it recognize the
vim
orrc
file types, if the previous entries are added with thefiles.associations
setting insettings.json
:Either of these would be a great addition.