From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _mutt, _mailboxes
Date: Thu, 16 Sep 1999 16:38:23 +0100 [thread overview]
Message-ID: <19990916163823.A17248@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199909161311.PAA01349@beta.informatik.hu-berlin.de>
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> And while I'm at it... I'm the only one who writes option
> descriptions, it seems, which I can understand considering how tedious
> that is. So my question is: if an option gets only one argument,
> should we turn it's description automatically into the
> option-description? Probably prefixed by something like `specify: '?
Sounds like a good idea. How about a configuration key which in this
case would be something like `specify: %s'?
Adam
next prev parent reply other threads:[~1999-09-16 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 13:11 Sven Wischnowsky
1999-09-16 15:38 ` Adam Spiers [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-17 11:22 Sven Wischnowsky
1999-09-17 9:04 Sven Wischnowsky
1999-09-15 21:30 Clint Adams
1999-09-18 23:27 ` Bart Schaefer
1999-09-20 4:48 ` Clint Adams
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=19990916163823.A17248@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).