From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: curtag (Re: can't run _email-mutt)
Date: Sun, 19 Jun 2005 17:09:13 +0000 [thread overview]
Message-ID: <1050619170913.ZM20484@candle.brasslantern.com> (raw)
In-Reply-To: <22509.1118076149@trentino.groupinfra.com>
Just got a chance to look at this ...
On Jun 6, 6:42pm, Oliver Kiddle wrote:
}
} Has anyone got any ideas on how to narrow the context for the plugin
} tag-order. Currently, if you want to specify a list of plugins as a
} global setting, you need a context like ':completion:*'. That's not
} nice but the best alternative is listing commands:
} ':completion:*:(mailx|Mail|mutt|mush|ali|netscape):*'
One possibility would be for _email_addresses to call
_tags -C email-addresses email-$plugins
which would make the context look like
:completion:*:*:*:email-addresses:*
} Ideally, _tags should allow me to put 'email-addresses' in as a tag. It
} should perhaps use $curtag.
I'm not sure how $curtag would apply in this case, because it's not set
until _requested or _wanted calls _all_labels from inside the _tags loop?
Or are we talking about nested _tags loops here, which is already a bit
of a sticky wicket?
It's entirely possible that there's some subtlety I'm missing.
On a more general note, though, it would appear that $curtag is rather
under-utilized. By a quick grep I count about 15 functions that use both
_tags and zstyle without reference to $curtag. _email_addresses is the
only one that seems to use it as it was intended.
next prev parent reply other threads:[~2005-06-19 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050527141638.GA9644@xpeerience.u-strasbg.fr>
[not found] ` <7779.1117444705@trentino.groupinfra.com>
[not found] ` <20050530135757.GA12204@xpeerience.u-strasbg.fr>
[not found] ` <13199.1117464233@trentino.groupinfra.com>
[not found] ` <20050602123718.GA21218@xpeerience.u-strasbg.fr>
2005-06-06 16:42 ` can't run _email-mutt Oliver Kiddle
2005-06-19 17:09 ` Bart Schaefer [this message]
2005-06-20 12:17 ` curtag (Re: can't run _email-mutt) 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=1050619170913.ZM20484@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).