From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: lei-q doc thoughts... [was: doc: start manpages for lei commands]
Date: Sun, 7 Feb 2021 03:33:33 +0000 [thread overview]
Message-ID: <20210207033333.GA21239@dcvr> (raw)
In-Reply-To: <874kipj7ft.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
>
> No, I can't either. Dropping --mua-cmd makes sense.
> Eric Wong writes:
> > Heh, it turns out mairix uses "--threads" (plural). I never
> > knew that since I always used "-t". Not sure if it's worth
> > pluralizing on our end...
>
> I'd vote for following mairix here. I guess most people will use -t,
> but it's just one less thing to get tripped up on.
Thanks, I'll queue up necessary patches for those.
> By the way, if you'd like, I'd be happy to do a round (or more) of lei
> manpage updates for new additions whenever you think things are in a
> good spot for it.
Yes, much appreciated, thanks in advance :>
Anything covered by tests should be considered
ready-for-documentation, I think. That can help us flush out
any strange/unexpected behaviors before it's finalized in a
release.
Fwiw, I'm likely to apply+push any doc-only patches as quickly as
I see them.
next prev parent reply other threads:[~2021-02-07 3: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 [this message]
2021-02-07 19:58 ` lei q --output vs --mfolder [was: [PATCH 1/2] " Eric Wong
2021-02-07 20:33 ` 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=20210207033333.GA21239@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).