From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12250 invoked from network); 29 Apr 1999 00:47:29 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Apr 1999 00:47:29 -0000 Received: (qmail 22031 invoked by alias); 29 Apr 1999 00:47:11 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6143 Received: (qmail 22023 invoked from network); 29 Apr 1999 00:47:05 -0000 From: "Bart Schaefer" Message-Id: <990428174435.ZM5142@candle.brasslantern.com> Date: Wed, 28 Apr 1999 17:44:34 -0700 In-Reply-To: Comments: In reply to Greg Badros "Re: alwayslastprompt bugs in 3.0.6-pre-2 (?)" (Apr 28, 2:47pm) References: <990428001558.ZM848@candle.brasslantern.com> <990428084314.ZM2839@candle.brasslantern.com> X-Mailer: Z-Mail Lite (5.0.0 30July97) To: Greg Badros Subject: Re: alwayslastprompt bugs in 3.0.6-pre-2 (?) Cc: zsh-workers@sunsite.auc.dk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 28, 2:47pm, Greg Badros wrote: > Subject: Re: alwayslastprompt bugs in 3.0.6-pre-2 (?) > "Bart Schaefer" writes: > > ESC-x backward[CTRL-D]-char[ENTER] > ^^^^^^^^ this shows the menu under the "execute:" prompt > > After pressing ENTER, only the first line of the menu is erased. The > rest disappears after the next prompt, but not while editing the current > line. Oh. Believe it or not, that's intentional. It was only changed recently in 3.1.5-pws-something when a whole slew of other commands were also added to the set of actions that completely clear the completion listing. > Also, when at the end of the xterm window (nxterm from RedHat 5.2, or > the latest xterm96 built from sources) once I hit the "b" in "backward" > above, a newline and a space get printed causing the text to scroll up > unnecessarily. Geoff can say for sure, but I think that's a side-effect of writing code that works OK on terminals whose termcap/info entries lie about the way automargin behaves on the last line of the display. In short, I don't think either of these counts as a bug.