Plugin appears not to get loaded by neovim

[dasteihn]

rust.vim version:

The issue appears to be very similar to issue 288, though I don't use the vim-css Plugin like the other guy did.

I use vimplug and rust.vim commit 9984b97
Editor is Neovim, version 0.1.7

Steps to reproduce:
Install the rust.vim and open a Rust-file

Expected vs. actual behavior:
It's expected to have working syntax highlighting. Instead, all that is highlighted for me are the brackets, everything else is treated as normal text.

Paste debugging info from the Rust Vim plugin via one of the following
commands: :RustInfo, :RustInfoToClipboard, or :RustInfoToFile <filename>.

The RustInfo(nor similar) command appears not to be found by nvim. Yet the PlugStatus indicates that the plugin is ready to use

Finished. 0 error(s).
[===]

- nerdcommenter: OK
- nerdtree: OK (not loaded)
- rust.vim: OK

Vimrc:

:set number
:colorscheme torte
:set colorcolumn=81,91
:set tabstop=4
:set smarttab
:set autoindent
:set shiftwidth=4
let g:airline_powerline_fonts = 0

let mapleader = ","

call plug#begin('~/.nvim/plugged')
Plug 'scrooloose/nerdtree', { 'on':  'NERDTreeToggle' }
Plug 'scrooloose/nerdcommenter'
Plug 'rust-lang/rust.vim'
call plug#end()

[mhinz]

1. Nvim v0.1.7 is pretty old. There were more than 5000 patches since then.
2. Is ~/.nvim a symlink? Because it's not a directory that Nvim checks by default. What ~/.vim is to Vim, is ~/.config/nvim to Nvim.
3. Use :scriptnames to see exactly which files got sourced.

[dasteihn]

1. That's the thing with Debian, you have age-old stuff. The awkward thing is that the plugin stopped working from one week to another.
2. No, that's a directory. But as most installation guides portray it it's the script file destination place for plugins
3. rust.vim gets loaded

It's notable that the other plugins work, so I'm not sure if there is a problem with the plugin folders

[mhinz]

:set filetype syntax shows rust in both cases?

---

But as most installation guides portray it it's the script file destination place for plugins

Not really. :) Of course you can pick any directory you want, vim-plug will adjust Vim's 'runtimepath' accordingly, but usually you place it under the default home runtime directory (~/.vim for Vim or ~/.config/nvim for Nvim. But yes, it really doesn't matter for this issue.)

[dasteihn]

No, filetype appears to be something called "hercules" for .rs files

Ok, I'll keep that in mind. Sadly, most instructions still aim at vim primarily, maybe that's why I didn't catch that earlier.

[mhinz]

Yeah, I guess it's related to the fact that the default filetypes detected by Nvim were updated not to set the hercules filetype for the file extention .rs two years ago.

[mhinz]

What's the output of :verb au BufRead *.rs?

[mhinz]

I can actually reproduce it with nvim from master but a runtime from 0.1.7.

The thing is.. you have two autocmds triggering for the .rs extension. But.. in your case the autocmd shipped by Nvim's filetype.vim comes first and only then the autocmd from rust.vim. So, the second :setfiletype used by rust.vim won't overwrite the hercules filetype set by filetype.vim.

This behaviour changed for you since this commit: 12f549f | #301

Until then, set filetype forced the filetype, but now :setfiletype won't anymore.

And for some reason, I can seem to work around that with this:

-  Plug 'rust-lang/rust.vim
+  Plug 'rust-lang/rust.vim', {'for': 'rust'}

Then, rust.vim gets sourced before filetype.vim (check :scriptnames) and so the setfiletype hercules fails.

[dasteihn]

The {'for': 'rust'} doesn't solve it for me, awkwardly.
I'm honestly surprised that using Debian stable causes so many trouble lately in general, as it's one of the most used distros

[mhinz]

Honestly, I haven't looked up the vim-plug code about why it changes the loading order for me, but the above-linked PR should fix the problem cleanly.