From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: $curcontext in _subscript
Date: Mon, 21 Feb 2000 14:12:06 +0100 (MET) [thread overview]
Message-ID: <200002211312.OAA05579@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Mon, 21 Feb 2000 13:04:02 +0000
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:<function>:<completer>:<command>:<arg>:<tag>'.
Where <command> 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
next reply other threads:[~2000-02-21 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 13:12 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-21 13:04 Oliver Kiddle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200002211312.OAA05579@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).