On Wed, 9 Jun 2010, Harald Dunkel wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/08/10 02:18, pac...@kosh.dhis.org wrote:
The root of the problem is that in non-UTF-8 mode, the \x9f character
eats an arbitrarily large sequence of non-control characters that follow it.
On 06/08/10 02:24, Thomas Dickey wrote:
http://invisible-island.net/xterm/manpage/xterm.html
(discussion of "-k8" option)
Is this a special xterm feature? "whois sensors.de" works much better
with -k8. Would you suggest to make -k8 the default?
... as a candidate feature, it's about on a par with
brokenLinuxOSC (class BrokenLinuxOSC)
If true, xterm applies a workaround to ignore malformed control
sequences that a Linux script might send. Compare the palette
control sequences documented in console_codes with ECMA-48.
The default is "true."
brokenSelections (class BrokenSelections)
If true, xterm in 8-bit mode will interpret STRING selections
as carrying text in the current locale's encoding. Normally
STRING selections carry ISO-8859-1 encoded text. Setting this
resource to "true" violates the ICCCM; it may, however, be use-
ful for interacting with some broken X clients. The default is
"false."
brokenStringTerm (class BrokenStringTerm)
provides a work-around for some ISDN routers which start an
application control string without completing it. Set this to
"true" if xterm appears to freeze when connecting. The default
is "false."
(the last, brokenStringTerm, is actually more pertinent to your use of
xterm than -k8)
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
