Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: unique partial completion
- X-seq: zsh-workers 3187
- From: <hzoli@xxxxxxxxxxxx> (Zoltan T. Hidvegi)
- To: schaefer@xxxxxxxxxxxxxxxxxxxxxxx (Bart Schaefer)
- Subject: Re: unique partial completion
- Date: Mon, 2 Jun 1997 16:41:39 -0400 (EDT)
- In-reply-to: <970602093746.ZM14926@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Jun 2, 97 09:37:46 am"
- Sender: <hzoli@xxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author