since filetypes_extensions.conf is not versionable better to use a completely different [Groups] name, maybe [Menu] because in existing files [Groups] will not have group_name_* and group_lang_* in it.

No problem with having [Menu] but the problem shouldn't exist as existing filetypes_extensions.conf under .config without these settings would just inherit them from the default filetypes_extensions.conf.

how will it interact with users existing filetype_extensions.conf that uses the existing group names?

Those will be ignored. Custom user-defined filetypes will appear in the "Other" fallback group unless assigned explicitly to some of the groups.

I would leave out the group_ or any other prefix, its in that section and doesn't need it.

Yeah, whatever, this was just a quick example.

Unless there is some reason the filetype is named different to the programming language (Fortran/F77 all I could find, but both are F) it should not be a problem I would have thought.

But when you have

A-G
H-L
M-Q
R-Z

and now say "quick, in which group is Python?", I'll know it's somewhere in the second half but will have to start going through the letters of the alphabet to be sure where P is exactly.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.