Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!igor!amber!geb
From: geb@amber.Rational.COM (Gary E. Barnes)
Newsgroups: comp.windows.x
Subject: Re: R2 xterm
Keywords: R2 xterm tek
Message-ID: <564@igor.Rational.COM>
Date: 12 Apr 89 19:08:05 GMT
References: <4003@ece-csc.UUCP> <521@pan.UUCP>
Sender: news@Rational.COM
Reply-To: geb@amber.Rational.COM (Gary E. Barnes)
Distribution: comp.windows.x
Organization: Rational, Santa Clara, CA
Lines: 31


I've managed to get xterm running on AIX under IBM's 2.2.1 X Windows.
What I did was take X11R2 xterm, diff it with X11R3 xterm, put in, by
hand, all changes that did not pertain to widgets or other XLib/XTk
interface changes, add a bunch of AIX specfic junque to make it work,
called IBM various times (they responded very nicely to my problems),
and it all worked.

If anyone is curious I can show them what to do AIX-wise.  IBM's X
Windows is a curious mixture of almost-X11R3 guts with a
definitely-X11R2 interface.  They have at least one XTk bug that is
unique to X11R3 but they still ship the X11R2 interface.

The full diffs between X11R2 xterm and our current hybrid are about
6000 lines long.  The AIX OS-specific stuff isn't too big/bad.  There
is some rather silly cruft that you have to do in order to disable
what they call HFT Emulation that things like vi and telnet keep
trying to force upon your poor unsuspecting pty port but most things
are relatively easy.

Another thing that you have to be aware of is that X11R2 and X11R3
have differences in the truth that they tell to an application about
textual extents and such.  The X11R3 code does a few "bad" things
since AIX is using the X11R2 textual stuff.  You get cursor ghosts and
descending characters leave droppings.  I've given our xterm some
switches, -/+X11R2 and -/+X11R3 so that you can tell it which text
model to use depending upon the server that you will be talking to.

Fun, huh?	Gary

Gary E. Barnes		geb@rational.com