zsh-workers
 help / color / mirror / code / Atom feed
From: <hzoli@VNET.IBM.COM> (Zoltan T. Hidvegi)
To: schaefer@candle.brasslantern.com (Bart Schaefer)
Subject: Re: unique partial completion
Date: Mon, 2 Jun 1997 16:41:39 -0400 (EDT)	[thread overview]
Message-ID: <9706022042.AA18246@belgium.fishkill.ibm.com> (raw)
In-Reply-To: <970602093746.ZM14926@candle.brasslantern.com> from Bart Schaefer at "Jun 2, 97 09:37:46 am"

Bart Schaefer wrote:
> On Jun 2,  8:40am, Anthony Iano-Fletcher wrote:
> } Subject: Re: unique partial completion
> }
> } > Just add unset LIST_AMBIGUOUS into your .zshrc.
> }
> } Thanks, that seems to work for me. :-)
> }
> } So far we have had 3 people who believe that the new default behaviour is
> } not entirely obvious. Why was this considered to make zsh more friendly?
>
> I don't think the problem is with listambiguous, I think it's with listbeep.
> I'm not sure, as I don't have 3.1.x compiled ... is listbeep no longer a
> default setting?  Or is it broken?

No, listbeep only beeps when a list is printed.  listambiguous does not
print a list if there is a unique partial completion hence there is no
beep.  Perhaps a new option is needed for that case.  The most difficult
question is how to call this new option.  Perhaps INCOMPLETE_BEEP?

Zoli


      reply	other threads:[~1997-06-02 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-30 12:53 Anthony Iano-Fletcher
1997-05-30 16:15 ` Zefram
1997-05-30 16:52   ` Bart Schaefer
1997-05-30 17:07     ` Anthony Iano-Fletcher
1997-05-30 17:21     ` Geoff Wing
1997-05-30 17:36       ` Anthony Iano-Fletcher
1997-05-30 18:00     ` Vinnie Shelton
1997-05-31  8:10 ` Zoltan Hidvegi
1997-06-02 12:40   ` Anthony Iano-Fletcher
1997-06-02 16:37     ` Bart Schaefer
1997-06-02 20:41       ` Zoltan T. Hidvegi [this message]

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=9706022042.AA18246@belgium.fishkill.ibm.com \
    --to=hzoli@vnet.ibm.com \
    --cc=schaefer@candle.brasslantern.com \
    /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).