[comp.windows.x] Problem with bash from an xterm on Apollo

sridhar@surya.usc.edu (M. A. Sridhar) (10/04/90)

I run X11R3 on an Apollo DN3000 with Domin/IX 10.2, and I use xterm to log into
a DECstation on the local net. And I built GNU's bash to run on the DECstation.
The problem is that when I run bash, and execute say ls -FC under it, about half
the output does not show up!

But bash behaves just fine when I dial in directly to the DECstation or log
into it directly. This seems to be a problem with Apollo's xterm combined with
bash. Has anyone else seen this? BTW, the version of bash I built is 1.05 
with patches, ftp'ed from uunet.uu.net. I tried rlogin'ing to another Sun
workstation that runs bash 1.01, but there things work just fine! I'm puzzled.

Any help is appreciated.


Sridhar

mouse@LARRY.MCRCIM.MCGILL.EDU (10/04/90)

> I run X11R3 on an Apollo DN3000 with Domin/IX 10.2, and I use xterm
> to log into a DECstation on the local net.

(Do you mean you run rlogin from within a local xterm, or you run xterm
remotely displaying on the Apollo?)

> And I built GNU's bash to run on the DECstation.  The problem is that
> when I run bash, and execute say ls -FC under it, about half the
> output does not show up!

Look more closely.  Try, in particular,

	% /bin/echo abcdefghijklmnopqrstuvwxyz

I predict you will see either

	abdghkmnpsuvyz

or

	cefijloqrtwx

(The following prompt may appear in a strange place, like on top of the
"ab" in the first example.)

If so, then look at your ls output.  Notice that each character ('a',
say) is either consistently present or consistently absent.  If this is
true, your problem is almost certainly parity.  Most likely, your stty
settings are set to generate parity bits, which are being passed
through rlogin to the xterm, which then botches them.  (It could be
ignoring them entirely, it could be trying to display nonexistent
characters from its font, or it could be doing something else; further
experimentation might be able to narrow down the possibilities.)

I seem to recall reading somewhere that some versions of bash have a
bug having to do with the "parity" bits of characters.  I don't know
whether this is related, but it might be worth looking into.  (Do
things still get dropped if you use another shell, like sh or csh?)

					der Mouse

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