On Wed, Jul 02, 2008 at 09:27:22PM +0100, David Chanters <[EMAIL PROTECTED]>
wrote:
> > Your problem is gnu screen not outputting the sequence, and that's
> > likely
> > a configuration issue.
>
> That's incorrect. GNU Screen does in fact output the correct sequence.
thanks for your explanations, all becomes much clearer now.
rxvt-unicode (like most terminals) uses the blink attribute for
high-intensity background when non-default text colours are used.
> My first guess was that perhaps rxvt-unicode confuses the "5" that would
> activate blinking text:
No, urxvt simply uses blink for something else when using indexed colour
mode (this is actually in complicance with ecma-48). This behaviour is
documented as well.
I didn't realise that the problem happened only in conjunction with
non-default text colours.
> So, I don't have answers to why this is the case, but it seems quite
> clear to me that the problem lies with rxvt-unicode, and not with screen
> (screen isn't even involved in any of the above tests).
It seems it is a user error - expecting blink to work in a specific way
that contradicts documentation. Blinking text only blinks in conjunction
with the default text colours.
> Eterm and rox-terminal I'm not very familiar with, but I suspect that
> there is an explicit decision not to support blinking in some terminals,
> as it is considered by many to be evil.
Which incidentally is also the reason why rxvt-unicode follows the
de-facto standard of using it for high-intensity background.
Thanks a lot for your epxlanations, the missing clue was indeed that this
only happened when using colours.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
