🚀 go-pugleaf

Does anyone have a version of GNU emacs running _well_ on a Stardent
(formerly Stellar and Ardent) workstation?  If so how?

Here's our situation:

we have a Stardent GS2000 and a GS2500 running Stellix Release 2.3.
Stardent supplies a version of GNU emacs version 18.50 as unsupported
software on these boxes.  However, this isn't a pristine version of
18.50, the Stardent folks have added some conditionally compiled
code to a few of the modules in addition to supplying the m- and s-
files.

This version works really well on the console or in a X window on
a remote (non-Stardent) machine.  However, it works poorly on 
other terminals (vt100/200, sun-cmd, xterm, iris-ansi-net, etc).
By poorly, I mean that what you see on the screen does not accurately
reflect the state of the buffer unless you do a ^L after every non-
trivial editting task.

Perhaps the problem is not with emacs at all, but with our termcap/terminfo
database.  Any experience out there on this?

I also tried to build the latest and greatest emacs (version 18.57)
in a vain hope that it would solve my problems.
As supplied by the GNU folks, it doesn't come with appropriate m-
and s- files, so I grabbed the old ones from the Stardentized  version of
emacs 18.50.  As expected, the out-of-the-box version of 18.57 didn't
compile as it had none of the conditionally compiled code in it that
Stardent had provided with 18.50.  Has anyone gotten this to work?
Is it sufficient to copy the Stardentized modules from version 18.50?
Is it worth the trouble?


					Thanks

					Scott Ray
					ray@icdc.llnl.gov
					ray4@llnl.gov

					(415) 423-0435