From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21050 invoked from network); 3 May 2000 14:46:07 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 May 2000 14:46:07 -0000 Received: (qmail 28373 invoked by alias); 3 May 2000 14:46:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11122 Received: (qmail 28326 invoked from network); 3 May 2000 14:45:58 -0000 Date: Wed, 3 May 2000 16:45:51 +0200 (MET DST) Message-Id: <200005031445.QAA06812@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Andrej Borsenkow"'s message of Wed, 3 May 2000 17:29:38 +0400 Subject: Re: Command completion Andrej Borsenkow wrote: > bor@itsrm2% nslo > Completing external command > nslookup > Completing shell function > nslookup > > This obviously makes no sense. We _may_ make completion so smart, as to > insert full pathname (or command) for external commands - but currently > nslookup will always execute functions, won't it? So, the above has one > unambiguous match? Hmhm. I'd still like to see that information for really unambiguous matches, but in cases like this one we should just go ahead and accept the single possible string. No patch yet... Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de