From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26408 invoked from network); 2 Jun 1997 21:09:45 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 2 Jun 1997 21:09:45 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id QAA03774; Mon, 2 Jun 1997 16:59:00 -0400 (EDT) Resent-Date: Mon, 2 Jun 1997 16:59:00 -0400 (EDT) From: (Zoltan T. Hidvegi) Message-Id: <9706022042.AA18246@belgium.fishkill.ibm.com> Subject: Re: unique partial completion In-Reply-To: <970602093746.ZM14926@candle.brasslantern.com> from Bart Schaefer at "Jun 2, 97 09:37:46 am" To: schaefer@candle.brasslantern.com (Bart Schaefer) Date: Mon, 2 Jun 1997 16:41:39 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: Resent-Message-ID: <"gf5Y02.0.vw.JGpap"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3187 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu 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