From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6623 invoked from network); 13 Sep 1999 13:31:15 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Sep 1999 13:31:15 -0000 Received: (qmail 15270 invoked by alias); 13 Sep 1999 13:31:03 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7803 Received: (qmail 15263 invoked from network); 13 Sep 1999 13:31:01 -0000 Date: Mon, 13 Sep 1999 15:30:59 +0200 (MET DST) Message-Id: <199909131330.PAA21257@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Andrej Borsenkow"'s message of Fri, 10 Sep 1999 20:19:48 +0400 Subject: Re: Problem with _arguments and _normal as action if nolistambiguous is set. Andrej Borsenkow wrote: > itsrm2% sudo -TAB > itsrm2% sudo <=cursor here This is a really ugly bug. It comes from the fact that the options are added with a `r:|-=*' match spec and commands are not. The completion code currently can't merge the unambiguous string information if the equal substrings are in an anchor for some matches and in a normal string-part for other matches. And the more I think about ways to solve this the more complicated it gets. So I'll need some more time. > TAB once more > > itsrm2% sudo !<=cursor Here the completion code starts completing the matches for command position. And they include the `!' (the `not' operaator/precommand specifier). > itsrm2% sudo !!<=cursor I don't get this doubled `!'. For me it just continues inserting command names and such things. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de