Here's the script in readable form (using unmap from my ncurses ftp area):
Script started on Mon Jun 13 17:24:24 2005
\n
\E]0;[EMAIL PROTECTED]:~^G\r
\E[0m
\E(
\E[27m
\E[24m
\E[Jpaul@
\E[1m
\E[37mpower
\E[0m
\E(
\E[0m%
\E[K
\E[80C ~
\E[82D
\E[K\r\r
\n
\nScript done on Mon Jun 13 17:24:26 2005
\n
The problem is that with the older ncurses before the fix mentioned for
20040710
...
+ modify logic in tgetent() which adjusts the termcap "me" string
to work with ISO-2022 string used in xterm-new (cf: 20010908).
...
20040626
...
+ modify xterm-new aka xterm-xfree86 to accommodate luit, which
relies on G1 being used via an ISO-2022 escape sequence (report by
Juliusz Chroboczek)
ncurses could only successfully chop out a single byte from the sgr0 string
(a fix made to allow screen to work properly). sgr0 for xterm-new is
sgr0=\E(B\E[m,
though this is also common (and equivalent)
sgr0=\E[m\E(B,
The example of the prompt above is probably the latter. Rather than
removing \E(B, ncurses removed only B.
The 27m's come about because of the way xterm handles errors. It's
predictable.
\E(
\E[27m
is missing the final character for \E(, so the next \E goes to an
error state, leaving the [27m printable.
--
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
