Summary: | wchar_t characters aren't highlighted as characters | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | greatbunzinni |
Component: | syntax | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
greatbunzinni
2007-07-28 00:29:45 UTC
Correction: characters such as L'c' seem to be, in fact, highlighted as characters. Those which aren't highlighted are those that are defined through an escape sequence, such as L'\x0000'. KDevelop has no editor, it uses kate so this is a bugreport for kate. (Really reassing to the Kate guys.) Do I understand right that string are detected correctly but you want the leading "L" to be in string color as well? Not quite. What I tried to say was that, unlike the case of regular character constants ('a', '1', etc...), if a character constant is described as a bit pattern through octal or hexadecimal encoding ('\x123', '\o123') then that notation will not be coloured as the regular, simple character constants. To put it simply, 'a' gets the constant syntax highlighting but '\x123' and '\o123' do not. Seems like I didn't read your correction, sorry. What you describe is actually a feature: people have done extra work to make escape sequences stand out. If you don't like that I guess the best way is to "fix" the highlighter on your end. Should be a five minute thing: all you need to do is change a line in the <itemDatas>. If you feel like this is what you need but cannot get it to work I can make you a patch. Feature, not a bug. |