After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 64073 - echoing the 7 bit 'OSC 0; %s ST' escape sequence hangs gnome-terminal
echoing the 7 bit 'OSC 0; %s ST' escape sequence hangs gnome-terminal
Status: RESOLVED FIXED
Product: gnome-core
Classification: Deprecated
Component: gnome-terminal
1.4.x
Other Linux
: Normal normal
: 1.4.1
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-11-08 17:43 UTC by Christian Marillat
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Recognise 2 character escape sequence terminator (640 bytes, patch)
2001-11-16 16:45 UTC, vivek
none Details | Review

Description Christian Marillat 2001-11-08 17:43:19 UTC
Hi,

There are certain escape sequences which, when echoed to stdout or stderr
(or even stdin, weirdly enough) by an application using an instance of a 
<thing sufficiently like an xterm to behave like one>, control the
behaviour
of said terminal-emulator. They are documented in 
'/usr/share/doc/xterm/ctlseqs.txt.gz', which is part of the xterm package.

There are symbolic names for the character sequences that make up these
control sequences, since they can exist in both 7bit encoded and 8bit
encoded forms.

The sequences: 

OSC 0; STRING BEL

and

OSC 0; STRING ST

which can be passed to the termianl program by the following echo commands:

echo -ne "\033]0;STRING\007"

and 

echo -ne "\033]0;STRING\033\\"

respectively, are both supposed to set the title of a <terminal emulator>
to STRING. The BEL terminated version of the sequence works in
gnome-terminal, but the ST terminated sequence does not - my first guess
would be that gnome-terminal does not recognise that the ST sequence 
terminates a control sequence, and therefore just sits there, witing for 
the command to complete, which of course it never does.

Therefore, if I launch a gnome terminal, it gets as far as trying to emit
the ST version of the sequence (my .bashrc does this), and just hangs.

This may well apply to other control sequences that have ST and BEL as 
alternative terminators.
Comment 1 vivek 2001-11-16 16:45:07 UTC
Created attachment 6031 [details] [review]
Recognise 2 character escape sequence terminator
Comment 2 vivek 2002-01-22 17:47:57 UTC
This is fixed by the patch committed against bug 65154 - if that patch
stays in, this one can be dropped.