(*** This bug was imported into bugs.kde.org ***) Package: kate Version: KDE 3.0.1 Severity: normal Installed from: Solaris Packages Compiler: GCC 3.1 OS: Solaris OS/Compiler notes: KDE taken from Eva's packages of ftp.kde.org Open a file in Kate with a name ending in .C or .H and its highlighting mode is set to C not C++. Under Configuration/Highlighting there is: C highlighting: Extensions: *.h;*.c Mime Types: text/x-chdr;text/x-csrc C++ highlighting: Extensions: *.hh;*.H;*.cpp;*.cxx;*.cc;*.C Mime Types: text/x-c++hdr;text/x-c++src With the highlighting as set above I would expect .C and .H files to be highlit as C++. (Submitted via bugs.kde.org)
we test the stuff caseinsensitive, therefor first match will win
Subject: Re: highlighting mode of *.[HC] is set to C not C++ despite MIME settings Christoph: I find your answer utterly amazing. KDE currently runs on Linux and various flavours of Unix. All of these have native file systems that do not perform case-folding on file names. Nevertheless, you *do* perform case folding on file names when determining MIME type, even though this does not model the reality correctly. It is analogous to saying that this function that I've written works on the absolute values of its numerical arguments, and that is why it doesn't work as the users expect, and that is alright ! Very strange . . . (None of the above should be taken as meaning that I am not grateful for the remarkable and generally excellent system that is KDE; I do however as you to reconsider your decision in this matter) ---- Original message -------------------------- ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. http://bugs.kde.org/show_bug.cgi?id=44144 crossfire@babylon2k.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From crossfire@babylon2k.de 2002-09-18 23:33 ------- we test the stuff caseinsensitive, therefor first match will win
If this bug isn't fixed yet, please fix it. If you test the extensions case-insensitively, then ***that*** is the bug. cheers domi
in the mean time it has settled over to case-sensitive comparisons