user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: lei q --output vs --mfolder [was: [PATCH 1/2] doc: start manpages for lei commands]
Date: Sun, 7 Feb 2021 19:58:29 +0000	[thread overview]
Message-ID: <20210207195829.GA7349@dcvr> (raw)
In-Reply-To: <20210201055704.26683-2-kyle@kyleam.com>

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?

(mairix uses '-o', so we match it there)

I never really got used to using "folder" to describe mailboxes
or directories.  I associate "folder" with something that holds
only a few pages of paper in the physical world; not thousands
or millions of items.

  parent reply	other threads:[~2021-02-07 19:58 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   ` Eric Wong [this message]
2021-02-07 20:33     ` lei q --output vs --mfolder [was: [PATCH 1/2] " Kyle Meyer
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=20210207195829.GA7349@dcvr \
    --to=e@80x24.org \
    --cc=kyle@kyleam.com \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).