That was an impressively fast reply!
Can you explain to me why the YAML format remains in the menu, even when I commented it out in the built-in filetype_extensions.conf? This was one reason I suspected some other hardcoded mechanism I can’t override
Skickat från min iPhone
23 juni 2019 kl. 23:48 skrev Colomban Wendling notifications@github.com:
You need to "unmap" YAML in filetype_extensions.conf. What you should do is in the user's filetype_extensions.conf add a YAML= line that does not include the extensions you want somewhere else.
The technical reason for this is that the system and user's files are merged, with the user's one overriding the system ones. Then, they are currently (this is NOT something to rely one!) matched alphabetically, so the first occurrence wins, and it happens that YAML sorts before YML. So if you just add the extensions to YML but don't remove them from YAML, the YAML match still wins. Arguably the user's file maybe should be tried first, and the system one only if the user's one didn't match, but for now it's not the case, and you should then make sure to unmap the extensions you want to reuse. It should be as easy as re-defining the offending line for it not to include these extensions.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.