Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: 1.03 teething pains
Message-ID: <8909072240.AA07452@aurel.caltech.edu>
Date: 7 Sep 89 22:40:35 GMT
References: <30004@gore.com>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 35


   Date: 7 Sep 89 06:01:00 GMT
   From: gore!jacob@boulder.colorado.edu  (Jacob Gore)
   Organization: Gore Enterprises
   References: <8909062316.AA08340@life.ai.mit.edu>
   Sender: bug-bash-request@prep.ai.mit.edu

   / 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

I'm sorry that this bug appeared in 1.03.  I will be posting patches for
this and a few other fixed bugs on Friday, Sep 8.

Thanks for being patient.

Brian