From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: lei q --output vs --mfolder [was: [PATCH 1/2] doc: start manpages for lei commands]
Date: Sun, 07 Feb 2021 15:33:04 -0500 [thread overview]
Message-ID: <871rdrzkhr.fsf@kyleam.com> (raw)
In-Reply-To: <20210207195829.GA7349@dcvr>
Eric Wong writes:
> Kyle Meyer <kyle@kyleam.com> wrote:
>> +++ b/Documentation/lei-q.pod
>
>> +=item -o PATH, --output=PATH, --mfolder=PATH
>> +
>> +Destination for results (e.g., C<path/to/Maildir> or - for stdout).
>
> Fwiw, I didn't really like the term "mfolder" but that's what
> mairix users are used to... Perhaps:
>
> =item -o MFOLDER, --output=MFOLDER
>
> Or is "mfolder" not that bad and we ditch --output instead?
Yeah, I don't like "mfolder" either. In the --thread{,s} case,
consistency seemed worth it to me because either one sounded okay, and a
one character difference is easy to not notice. But in this case, I
think --output is the better name, so if we're dropping one, I'd vote to
cast out --mfolder.
Using MFOLDER rather than PATH as the metavariable seems a bit confusing
to me because the target isn't a directory for --format values other
than "maildir".
next prev parent reply other threads:[~2021-02-07 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:57 [PATCH 0/2] doc: initial lei manpages Kyle Meyer
2021-02-01 5:57 ` [PATCH 1/2] doc: start manpages for lei commands Kyle Meyer
2021-02-06 9:01 ` lei-q doc thoughts... [was: doc: start manpages for lei commands] Eric Wong
2021-02-06 19:57 ` Kyle Meyer
2021-02-07 3:33 ` Eric Wong
2021-02-07 19:58 ` lei q --output vs --mfolder [was: [PATCH 1/2] " Eric Wong
2021-02-07 20:33 ` Kyle Meyer [this message]
2021-02-07 20:59 ` Eric Wong
2021-02-07 21:47 ` Kyle Meyer
2021-02-07 21:55 ` Eric Wong
2021-02-01 5:57 ` [PATCH 2/2] doc: add lei-overview(7) Kyle Meyer
2021-02-01 6:40 ` Eric Wong
2021-02-01 11:37 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rdrzkhr.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).