Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!samsung!xylogics!transfer!lectroid!pretzel.sw.stratus.com!jberk
From: jberk@pretzel.sw.stratus.com (Joe Berkovitz)
Newsgroups: comp.windows.x
Subject: Re: xterm/eightBitInput not implemented?
Keywords: If it is, what does it do? Possible bug fix. (X11R4/FIX11/GCC)
Message-ID: <1461@lectroid.sw.stratus.com>
Date: 4 Jun 90 21:28:25 GMT
References: <1545@gmuvax2.gmu.edu>
Sender: usenet@lectroid.sw.stratus.com
Reply-To: jberk@pretzel.sw.stratus.com (Joe Berkovitz)
Organization: Stratus Computer, Inc.
Lines: 21

In article <1545@gmuvax2.gmu.edu>, rauletta@gmuvax2.gmu.edu (R. J.
Auletta) writes:
|>I have two questions. First, what exactly is the intent of this
|>resource. Does it cause extended characters not to be displayed
|>or does it strip the 8th bit so that the 7 bit code is displayed?
|>

Near as I can tell, the eightBitInput resource determines whether the Meta key
modifier plus a character code
	-- causes the 8th bit to turned on (resource = true, the default), or...
	-- precedes the character with an ESC (resource = false).

I set the resource to false because I prefer using the Meta key to
hitting an ESC prefix.  This is the way pre-R4 xterm behaved.

|>I also feel the default for this resource should be false.

I second that!

Joe Berkovitz
jberk@pretzel.sw.stratus.com