Bug 355990

Summary: Syntax highlighting for *.conf files not working
Product: [Applications] kate Reporter: Unknown <null>
Component: kwriteAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: christoph, ilmari.lauhakangas
Priority: NOR    
Version First Reported In: 16.04.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Unknown 2015-11-27 13:37:51 UTC 
Syntax highlighting for *.conf files not working

Reproducible: Always

Steps to Reproduce:
Open a .conf file in Kate/Kwrite


Actual Results:  
No syntax highlighting

Expected Results:  
Correct syntax highlighting

Version 15.08.3

Using:
KDE Frameworks 5.15.0
Qt 5.5.0 (built against 5.5.0)
The xcb windowing system

openSUSE Leap 42.1 using Plasma 5, all updated
Comment 1 Buovjaga 2016-06-27 08:13:08 UTC 
Conf-firmed.

Arch Linux 64-bit
Kate 16.04.2
KDE Frameworks 5.23.0
Qt 5.7
xcb wm
Comment 2 Christoph Cullmann 2016-09-06 12:10:19 UTC 
What is .conf?
I am not aware of "one" .conf content standard, on my system I find ini style, xml style, something style files, therefore I don't see how to fix that.
If there should be better content based detection, file a bug to mime magic.
Comment 3 Unknown 2016-09-08 17:23:07 UTC 
A .conf file is the same which vim and other text editors successfully add syntax highlighting to.
Comment 4 Christoph Cullmann 2016-09-08 17:28:49 UTC 
That comment doesn't help.
I have pointed out: alone on my machine, I have "*.conf" files with completly different formats.
Therefore I can't add a highlighting for this.
For some .conf mime magic might detect the right mime-type, then you have the right highlighting, else not.
Just do a find in etc for *.conf, you will find a wild mix of things.
Comment 5 Unknown 2016-09-08 17:32:45 UTC 
How do vim and others do it then?