Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!pyrdc!gmu90x!gmuvax2!rauletta
From: rauletta@gmuvax2.gmu.edu (R. J. Auletta)
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: <1550@gmuvax2.gmu.edu>
Date: 3 Jun 90 22:18:18 GMT
References: <1545@gmuvax2.gmu.edu>
Reply-To: rauletta@gmuvax2.UUCP (R. J. Auletta)
Organization: George Mason Univ. Fairfax, Va.
Lines: 36

In article <1545@gmuvax2.gmu.edu> rauletta@gmuvax2.gmu.edu (R. J. Auletta) writes:
>
>The X11R4/Fix11 xterm manual describes a resource eightBitInput.
>
>Here is my dirty little hack. I assume there is a better place

......Which does not handle non-printing characters correctly. A better
hack for just the VT100 window is to make the following changes
to charproc.c in VTparse:

        switch ( parsestate[
                c = screen->eight_bits ? doinput() : 0x7f & doinput() ])
                {
                 case CASE_PRINT:
                        /* printable characters */
                        top = bcnt > TEXT_BUF_SIZE ? TEXT_BUF_SIZE : bcnt;
                        cp = bptr;
                        *--bptr = c;
                        while(top > 0 && isprint(*cp & 0x7f)) {

                                if(screen->eight_bits == 0)
                                        *cp &= 0x7f;
                                top--;
                                bcnt--;
                                cp++;
                        }


I assume a similar change could be made to the Tek window.

As always suggestions, comments, or the correct solution would
be greatly appreciated. BTW, has anyone noticed that when xterm
is built with gcc.1.36, calling up the tek window causes a bus error?

--Rich Auletta
  rauletta@gmuvax2.gmu.edu