misleading information filetype.txt help doc about neovim

[clason]

However, I was curious if ex_filetype still sources that file on purpose for backwards compatibility (in case the user has a filetype.vim file in her runtime path).

Yes, precisely.

And note that this help file is part of the Vim manual, which we only edit for factual, objective inaccuracies. This means that most of these improvements apply to Vim as well and should be made there first.

[rphodges]

For Vim, really the only thing that's missing is a reference to the sourcing of ftdetect/* vimscript files. I'll consider making a proposal to them to include it. It could go into detail about how the scripts.vim uses shebang lines and other file contents to determine the filetype but it's not factually incorrect.

For NeoVim however, the logic for using the shebang line and other contents of the file to detect filetype is all built into filetype.lua rather than a scripts.vim file. It's a much cleaner design.

In Neovim, the scripts.vim and filetype.vim files are really only sourced for backwards compatibility. I'll write up some text that makes this more clear. I'll understand if you really want the manual to stay as close to the Vim reference manual as possible.

[clason]

I'll understand if you really want the manual to stay as close to the Vim reference manual as possible.

That is the general idea, yes. (There are many, many, places in the manual that could be rewritten for Neovim, and we have refrained from doing so until now in order to be able to more easily include documentation improvements from Vim.)