zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Greg Badros <gjb@cs.washington.edu>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: alwayslastprompt bugs in 3.0.6-pre-2 (?)
Date: Wed, 28 Apr 1999 18:38:36 -0700	[thread overview]
Message-ID: <990428183837.ZM5331@candle.brasslantern.com> (raw)
In-Reply-To: <qrr676gxme7.fsf@elwha.cs.washington.edu>

On Apr 28,  6:09pm, Greg Badros wrote:
> Subject: Re: alwayslastprompt bugs in 3.0.6-pre-2 (?)
> "Bart Schaefer" <schaefer@brasslantern.com> writes:
> 
> Can someone justify to me why it's better to not clear the completion
> listing for Esc-X?

Probably not, because it's not better.  That's why it changed in 3.1.5+.
The issue is that there are a number of other commands that don't clear
the completion list for which that's also sub-optimal, so it's hard to
justify fixing any one of them, and harder to justify fixing all of them.

However, if Sven (or anyone else) sends a patch, I'll include it.


  parent reply	other threads:[~1999-04-29  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28  7:15 Release candidate patch for 3.0.6 Bart Schaefer
     [not found] ` <qrrbtg9171h.fsf@elwha.cs.washington.edu>
1999-04-28 15:43   ` alwayslastprompt bugs in 3.0.6-pre-2 (?) Bart Schaefer
     [not found]     ` <qrryajczabg.fsf@elwha.cs.washington.edu>
1999-04-29  0:44       ` Bart Schaefer
     [not found]         ` <qrr676gxme7.fsf@elwha.cs.washington.edu>
1999-04-29  1:38           ` Bart Schaefer [this message]
1999-04-29  2:14             ` Bart Schaefer
     [not found]   ` <990429112806.ZM9027@candle.brasslantern.com>
1999-04-29 21:51     ` colorized completion patch [was Re: Release candidate patch for 3.0.6] Greg Badros
1999-04-29  6:52 alwayslastprompt bugs in 3.0.6-pre-2 (?) Sven Wischnowsky
1999-04-29 14:04 ` Geoff Wing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=990428183837.ZM5331@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=gjb@cs.washington.edu \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).