From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16923 invoked from network); 21 Feb 2000 13:12:13 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 21 Feb 2000 13:12:13 -0000 Received: (qmail 10026 invoked by alias); 21 Feb 2000 13:12:08 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9820 Received: (qmail 10019 invoked from network); 21 Feb 2000 13:12:07 -0000 Date: Mon, 21 Feb 2000 14:12:06 +0100 (MET) Message-Id: <200002211312.OAA05579@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Oliver Kiddle's message of Mon, 21 Feb 2000 13:04:02 +0000 Subject: Re: $curcontext in _subscript Oliver Kiddle wrote: > In my .zshrc, I have zstyle to define a tag-order of 'indexes parameters' for -subscript- because I don't want it to complete all variables after something like '$path['. This stopped working a while ago. I hope you really mean `indexes' and -- in a separate word -- `parameters'. Otherwise this would mean they should both be tried immediatly and together... > It seems that when _subscript is run, $curcontext is ':complete:-subscript-'. Why is 'completion' not in there as the first bit. As far as I can tell, 'complete' is put there by the complete completer. Because its given in the calls to zstyle. > What exactly should I be using as the parameters to zstyle to achieve this: it works with '*-subscript-*' but I'd prefer to use something more specific. Always remember that now the context names simply and cleanly always have the fixed format: `:completion:::::'. Where may also be one of the special contexts. So, what you want is: zstyle ':completion:*:*:-subscript-:*' tag-order indexes parameters Bye Sven P.S.: But just being able to define such things is fun, isn't it? -- Sven Wischnowsky wischnow@informatik.hu-berlin.de