Bug 252572 - selected text doesn't honor unchecked "Draw intense colors in bold font"
Summary: selected text doesn't honor unchecked "Draw intense colors in bold font"
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 18:58 UTC by Ivan D Vasin
Modified: 2011-04-01 17:18 UTC (History)
0 users

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 Ivan D Vasin 2010-09-27 18:58:46 UTC
Version:           2.5 (using KDE 4.5.1) 
OS:                Linux

i have my Konsole profile set up so that "Draw intense colors in bold font" is unchecked on the Appearance tab.  this setting is honored, for example, in the output of `ls --color=auto`, but it is ignored if i select text in that output.  in other words, intense colors are still rendered bold within selected text.

this is particularly problematic when using a font (e.g. Inconsolata) whose bold width is larger than its regular width.  as described in bug #226308, this causes parts of the output to become illegible.

Reproducible: Always

Steps to Reproduce:
1. navigate to Settings -> Configure Profiles... -> Edit Profile... -> Appearance.
2. uncheck "Draw intense colors in bold font".
3. click OK.
4. click OK.
5. $ ls --color=auto
6. select some of the output with the mouse.

Actual Results:  
intensely colored text within the selection is bold.

Expected Results:  
intensely colored text within the selection is not bold.
Comment 1 Christoph Feck 2010-09-27 20:50:28 UTC
I cannot reproduce on trunk.
Comment 2 Kurt Hindenburg 2010-10-12 03:52:34 UTC
I can't reproduce in 4.5.2 with the fonts I have.

I don't have Inconsolata, are you using that as well?
Comment 3 Ivan D Vasin 2011-04-01 17:18:14 UTC
i'm pretty sure this was still present in 4.5.4, but it's fixed in 4.6.1.