On 2021-05-21, Nicola
For some reason, the vim module has stopped highlighting code associated to custom filetypes (it still works for built-in filetypes).
I think I have found the culprit. In t-vim.tex, lines 63-88, Vim is called with --clean. That option appears *after* -u, effectively overriding it. Moving --clean as the first option (or, better, removing it) solves my issue. Some remarks. The module has this comment: --clean % dont load scada [sic] file (nvim) If the purpose of the option is to avoid loading a shada file, `-i NONE` (which is already there) should be enough. In Vim, --clean is not strictly necessary, because it is effectively a shorthard for `-N -i NONE --noplugin`. In Neovim, the meaning might be slightly different. Which brings me to the next paragraph. My recommendation would be not to care about Neovim. It is *not* a drop-in replacement for Vim and not meant to be compatible with Vim (it has already diverged from Vim in significant ways). Supporting both is likely going to become more and more difficult as time goes by. Anyway, if you do want to support both, I'd suggest at least to segregate the two commands, even if currently they may be (almost) identical. Hope this helps! Nicola