From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: docs (finally)
Date: Wed, 17 Nov 1999 12:28:49 +0000 [thread overview]
Message-ID: <19991117122849.C6248@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199911170954.KAA02005@beta.informatik.hu-berlin.de>
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> - And finally: I haven't converted the parameters used into styles
> yet. But I really think we should do that. Consider the `*_accounts'
> parameters. Here we look at `my_accounts', `other_accounts' and
> `<command>_accounts'. I think it would be nice to replace this with,
> e.g., a pseudo tag `account' and the styles `mine' and `other' (or
> something like that). We could then use the normal context-name
> matching mechanism that is used for all styles as the replacement
> for the `<command>_accounts' stuff. I.e., you could do:
>
> compstyle '*:accounts' mine ... # global default for my accounts
> compstyle '*:accounts' other ... # global default for other accounts
> compstyle '*:telnet*:accounts' mine ... # my accounts for telnet
>
> That'd be nice, wouldn't it?
I wrote the original *_accounts and for what it's worth, yes, I think
that would be very nice indeed; in fact I was very tempted at the time
to implement configurability similar (in principle at least) to this,
but now we have a very nice way of doing it properly. Yum.
> Ok, please have a look at the manual and tell me if/what you don't
> like (or what you *do* like ;-).
I'm saving all your recent _tags changes and I will go through them
when I get the time, I promise :-) I'm looking forward to getting my
teeth into some obviously juicy improvements. From reading some of
your pleas for feedback, I imagine it must feel like you're
simultaneously talking to Bart and a brick wall at the moment ;-)
prev parent reply other threads:[~1999-11-17 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-17 9:54 Sven Wischnowsky
1999-11-17 12:28 ` Adam Spiers [this message]
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=19991117122849.C6248@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--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).