🚀 go-pugleaf

I posted a message earlier about how line editing gets messed up in a
login shell, but never messes up if the shell is a non-login shell,
even if the shell was started with the -login flag.  I never saw a
reply, so I don't know what the status of this one is.  Anyway, if
anybody is interested, I have a little more information:
Line editing (and future stdout output from bash) can be deranged on
my machine if, during line editing, a non-alphanumeric character (not
a number or a capital or small letter), including space, is deleted
either by rubout or ^D.  From then on, on that line, the first character
inserted _after_ a non-alphanumeric will be lost.  Further characters
will be put on the line as they are typed, except for repeated presses
of the same non-alphanumeric (in which case, none of the characters
is displayed).  In addition, if a non-alphanumeric was deleted
anywhere on the line, the next alphanumeric (usually) character, and
all non-alphanumerics preceding it are missing in the next output to
stdout.

I am running on a uVax II under Ultrix 2.0.

Hope this helps.

--

Andrew Thomas
andrewt@watsnew.waterloo.edu	Systems Design Eng.	University of Waterloo
"If a million people do a stupid thing, it's still a stupid thing." - Opus