From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7910 invoked from network); 11 May 2002 10:48:24 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 11 May 2002 10:48:24 -0000 Received: (qmail 23593 invoked by alias); 11 May 2002 10:48:15 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17124 Received: (qmail 23582 invoked from network); 11 May 2002 10:48:15 -0000 From: Borsenkow Andrej To: Zsh hackers list Subject: tag-order problem Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3-1mdk Date: 11 May 2002 14:48:00 +0400 Message-Id: <1021114086.27414.10.camel@localhost.localdomain> Mime-Version: 1.0 Just found problem in my _service/_services _service calls _services to complete list of available services. Because _services normally completes both init and xinetd, I presumed I could limit matches by setting tag-order; in this case: zstyle :completion::complete:service:argument-1: tag-order init - (meaning - for the first argument of service somplete only tag `init'). It did restrict services set to init only - but it also stopped dead options completion. Setting tags to `options init -' does allow options completion - both in first and second word as well; third and subsequent are completed normally (after -TAB three times: {pts/2}% service --debug --full-restart httpd-naat Completing init services httpd-naat syslog-ng Looking in traces, it seems that _arguments in _service correctly setups requested tags (that are argument-1 and options) and does not use the above tag-order style at all first call to _tags in tags loop is O.K.; next `_requested argument-1' also returns true next call to _tags is still true but call to `_requested options' fails. If no tag-order is defined it works correctly but then both sets are listed (that I'd like to avoid). -andrej