Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: xterm/eightBitInput not implemented?
Message-ID: <9006040311.AA18728@Larry.McRCIM.McGill.EDU>
Date: 4 Jun 90 03:11:10 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 21

>> The X11R4/Fix11 xterm manual describes a resource eightBitInput.
>> Here is my dirty little hack.

> ......Which does not handle non-printing characters correctly.

Depends on your notion of "correctly".  If I told it to disable
8-bitness, I would expect the 0x80 bit to be stripped from every byte
coming up the pty, including nonprinting characters and those forming
escape sequences.

> BTW, has anyone noticed that when xterm is built with gcc.1.36,
> calling up the tek window causes a bus error?

This is due to calling some routine (CopyISOLatin1Lowered, I think it's
called) asking it to copy into a string literal.  Compile with
-fwritable-strings, that's a quick patch-around.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu