No subject

The culprit seems to be the attrcolor b ".I" line. According to the screen
docs, this means approximately "modify characters marked as bold to have a
high-intensity background of the current color." The screen manual may be
partially at fault because it gives this same example described as: "Use bright
colors for bold text. Most terminal emulators do this already.", while in the
previous paragraph the capital "I" is described as a pseudo-attribute which
alters the background rather than foreground color. Both resetting the color
with "attrcolor b", or using the correct attribute of 'attrcolor b ".i"' makes
things show up correctly.

I don't have xterm installed but urxvt seems to ignore the attrcolor setting,
and if xterm does the same that would explain why the reporter only noticed
this in Konsole.

Interestingly, my Konsole behaves reverse of what's reported. If TERM=xterm in
the Bash environment screen is run from, then bold colors are not intense
regardless of attrcolor setting. If TERM=xterm-256color then they show as
intense just as they would outside of screen.This may yet be a valid bug as I'm
unsure why setting the background color to intense for bold text would negate
the intense foreground color.

See:
http://www.gnu.org/software/screen/manual/screen.html#Attrcolor
http://www.gnu.org/software/screen/manual/screen.html#String-Escapes

Though I think the bug being discussed is unrelated, this recent mailing list
post helped clear things up too:
http://lists.kde.org/?l=konsole-devel&m=127811329005415&w=2

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.