Bug 143399 - highlighter text style: can't turn off inherited attributes
Summary: highlighter text style: can't turn off inherited attributes
Status: RESOLVED FIXED
Alias: None
Product: frameworks-syntax-highlighting
Classification: Frameworks and Libraries
Component: framework (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 247986 281694 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-23 20:04 UTC by Matthew Woehlke
Modified: 2020-01-03 18:04 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.62.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Woehlke 2007-03-23 20:04:58 UTC
Version:           svn branches/3.5 (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.1) 
OS:                Linux

Given a highlighting Attribute for which the default style (e.g. dsError) has an attribute enabled (e.g. underlined), I am unable to disable that attribute for that Attribute (note the case - capitalized = the entity in the .xml, lowercase = 'underlined', 'bold', etc.).

Offhand guess: the config doesn't have a way to save that an attribute should be cleared for a given Attribute.
Comment 1 Adrián Chaves (Gallaecio) 2012-10-24 18:16:37 UTC
Could you please confirm whether or not this applies to a recent version of Kate? And, if it still does, is this really a bug report, or is it a feature request?
Comment 2 Christoph Cullmann 2012-11-03 15:37:07 UTC
*** Bug 247986 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Cullmann 2012-11-03 15:39:33 UTC
*** Bug 281694 has been marked as a duplicate of this bug. ***
Comment 4 Dominik Haumann 2013-04-09 10:54:00 UTC
Still reproducible with dsError.
Comment 5 Christoph Cullmann 2019-08-25 10:36:15 UTC
Work on this has started. e.g. https://phabricator.kde.org/D23422
Comment 6 Dominik Haumann 2020-01-03 14:42:53 UTC
@Nibaldo: isn't this fixed?
Comment 7 Nibaldo G. 2020-01-03 17:49:21 UTC
Yes, it's fixed!