screen-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[RH#130510] Not setting hardstatus with TERM=gnome


From: Daniel Reed
Subject: [RH#130510] Not setting hardstatus with TERM=gnome
Date: Mon, 23 Aug 2004 11:11:00 -0400 (EDT)

---------- Forwarded message ----------
Date: Fri, 20 Aug 2004 20:15:14 -0400 (EDT)
From: Daniel Reed <address@hidden>
To: address@hidden
Subject: [RH#130510] Not setting hardstatus with TERM=gnome

[From https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130510]

  Description of problem:
  The gnome-terminal window title is not used for messages when using
  screen.  I think this is probably something to do with TERM=gnome (the
  now default setting), but I don't know exactly what.

  Version-Release number of selected component (if applicable):
  screen-4.0.2-4


screen-4.0.2/termcap.c:223 sets D_CXT to 1 if termname contains "xterm" or
"rxvt". D_CXT is used to determine whether to send xterm title escape sequences
in display.c's SetXtermOSC().

Recent versions of gnome-terminal do support xterm titles, but set TERM to
"gnome" instead of "xterm" due to several incompatibilities between
gnome-terminal and what xterm describes.

I do not believe there is a termcap/terminfo capability for xterm titles, so
screen is not necessarily doing anything wrong by hardcoding the terminal types
it thinks support xterm titles. However, hardcoding may not be optimal
long-term.

Should screen be extended to include "gnome" (and possibly "kterm", "konsole",
etc.) in the list of terminals it thinks support xterm titles, or might there
be a more reliable mechanism to use to allow terminals to convey that to
screen?

-- 
Daniel Reed <address@hidden>    http://people.redhat.com/djr/   Desktop and 
Cygwin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]