Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gatech!ncar!boulder!gore!jacob
From: jacob@gore.com (Jacob Gore)
Newsgroups: gnu.bash.bug
Subject: Re: 1.03 teething pains
Message-ID: <30004@gore.com>
Date: 7 Sep 89 06:01:00 GMT
References: <8909062316.AA08340@life.ai.mit.edu>
Reply-To: jacob@gore.com (Jacob Gore)
Organization: Gore Enterprises
Lines: 21

/ gnu.bash.bug / jjd@alexander.bbn.com (James J Dempsey) / Sep  6, 1989 /
> 1.03 sometimes drops or misorders (!) the first few characters I
> type just after I switch into an xterm window running bash 1.03.  This
> didn't happen in 1.02.

Interesting.  It's also happening on the NeXT -- I never saw characters get
misordered, but one or two characters from the first three (sometimes the
first and the third) get dropped.  This happens not only while switching
windows: going back to a key window running bash after it's been idle for a
while (and probably got swapped out to make room for background processes)
does it.  Almost every time.

> Under 1.03, typing ~brianf<tab> results in bash
> completing ~brianfox with no slash and my cursor after a space after
> the 'x'.

On NeXT, too.

Jacob
--
Jacob Gore	Jacob@Gore.Com		{nucsrl,boulder}!gore!jacob