2008/6/29 Marc Lehmann <[EMAIL PROTECTED]>: > On Sat, Jun 28, 2008 at 10:34:29PM +0100, David Chanters <[EMAIL PROTECTED]> > wrote: >> > Your problem is gnu screen not outputting the sequence, and that's likely >> > a configuration issue. >> >> Ah --- so does this explain then why the sequence works fine in XTerm >> and not in rxvt-unicode? That being the case, I am confused. > > Which sequence? The sequence to enable blinlking works fine in *both* > urxvt and xterm, right? Your problem seems to be that the sequence does
Yes. For example, if i do: echo -e '\033[5mhello' In both urxvt and xterm, it all works fine, and it blinks away quite happily. > not work in *gnu screen* so far, so it is unclear what you mena with > "doesn't work in urxvt-unicode". Well, i wouldn't know what sequence gnu screen would need to send in order to blink text. as i said, the sequence gnu screen sends when there are no color definitions to change the background color of the hardstatus in gnu screen works fine -- and it blinks happily (by default, the background color of the hardstatus in gnu screen uses reverse video -- it is in this scenario the blinking works). if i explicitly tell gnu screen to render a background color for the hardstatus, then whatever sequence is sent *fails* to blink in rxvt-unicode. It is this scenario which puzzles me --- since when running screen in XTerm, and changing the background of the hardstatus then it *does* blink --- so to my mind, there is something in this sequence which gnu screen sends which *is* working and being interpreted fine by xterm, but not by rxvt-unicode in this case. Hence my original question. Just for completeness' sake, i have asked a similar question on the gnu screen mailing list. Thanks for your help so far, Marc. David _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
