Bug 223081 - Konsole doesn't do bold in 256-color mode
Summary: Konsole doesn't do bold in 256-color mode
Status: RESOLVED DUPLICATE of bug 274603
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-17 07:32 UTC by Ryan Thompson
Modified: 2011-09-25 03:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Thompson 2010-01-17 07:32:29 UTC
Version:            (using KDE 4.3.4)
Compiler:          gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

When in 256-color mode, konsole will not show bold text using "intense" colors. It just uses the normal colors. This causes problems, because some text becomes invisible in some programs.
Comment 1 Ryan Thompson 2010-07-11 07:47:53 UTC
Bug is still present in KDE 4.5 packages from Kubuntu PPA
Comment 2 Daniel Hahler 2011-03-20 15:49:23 UTC
I have the problem that a ctermfg=15 highlight in Vim is "bright white" (#fff) when using "cterm=none", but grayish when using "cterm=bold" - it appears to use color 8 then instead.

I am not sure if this is what you've meant Ryan, but assuming it is, I will confirm this.

Let me know if you need some help for reproducing this, but in can be easily triggered in Vim using a highlight like this:
    hi StatusLine   ctermfg=15 cterm=bold
Comment 3 Jekyll Wu 2011-09-21 04:30:33 UTC
I think this bug is closely related with bug #274603, which has been fixed recently.

My experiment shows this is also fixed, but I am not sure. Can you check with the git version to see whether this is also fixed?
Comment 4 Jekyll Wu 2011-09-25 03:18:20 UTC
OK, I am now pretty sure this is a duplicate of #274603. Feel free to open if it is not a duplicate or not fixed in the devel version.

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