Bug 281694 - Kate Highlighting changes from default are not saved if colors are not changed
Summary: Kate Highlighting changes from default are not saved if colors are not changed
Status: RESOLVED DUPLICATE of bug 143399
Alias: None
Product: kate
Classification: Applications
Component: syntax (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR minor
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-09 15:43 UTC by g2spot
Modified: 2012-11-03 15:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description g2spot 2011-09-09 15:43:27 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

The default style (in 'Normal Text Styles') for comments is set to be italic.
I remove in 'Highlighting Text Styles' for my specific language (Hardware/VHDL in this case) the 'italic'. The the flag on 'use default' is removed too. But the change is not applied and not saved. Whenever I close the settings dialog and reopen it, 'italic' is still set as well as 'use default'. However when I remove the 'italic' and one of the colors as well, the setting is applied and saved.
Then I reset the 'use default' flag and all is back to like before my changes. Then I remove again the 'italic', it is saved an applied. So it fails only the first time I do that change.
Maybe it is useful to know that I use a color schema where VHDL has not been defined before...

Reproducible: Couldn't Reproduce

Steps to Reproduce:
-


Expected Results:  
Changes in 'Highlighting Text Styles' are always saved.

OS: Linux (x86_64) release 2.6.38-10-generic
Compiler: gcc
Comment 1 Dominik Haumann 2012-02-27 13:36:44 UTC
Can you please try again with a newer version? Maybe even quickly build it by following http://www.kate-editor.org/get-it
Comment 2 Christoph Cullmann 2012-11-03 15:39:33 UTC
Yeah, this is still an issue, sorry :(

*** This bug has been marked as a duplicate of bug 143399 ***