Skip to content

Show Custom Filetypes on config page

Jan Paul Batrina requested to merge work/custom-filetype-fix into master

commit cee9d964 added validation to filter out filetypes with invalid/missing highliting definitions, but only the default filetypes (one per highlighting definition) was added to the list.

BUG: 417507

I'm not sure if that commit is what exactly introduced the problem (maybe the problem is elsewhere/further down the stack), git blame showed that it contains the last changes on relevant lines, and the big report was submitted later.

Tested by appending the following to ~.config/katemoderc (only the 2 valid custom filetypes should be shown):


[Invalid Custom Filetype]
Highlighting=Invalid Highlighting
Highlighting Generated=false
Highlighting Version=
Indenter=
Mimetypes=
Priority=0
Section=
Variables=kate:\s
Wildcards=

[Valid Custom Filetype1]
Highlighting=
Highlighting Generated=false
Highlighting Version=
Indenter=
Mimetypes=
Priority=0
Section=
Variables=kate:\s
Wildcards=

[Valid Custome Filetype2]
Highlighting=Kconfig
Highlighting Generated=false
Highlighting Version=
Indenter=
Mimetypes=
Priority=0
Section=
Variables=kate:\s
Wildcards=
Edited by Christoph Cullmann

Merge request reports