From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: does "lei q" --format/-f need to exist?
Date: Thu, 18 Feb 2021 12:07:22 +0000 [thread overview]
Message-ID: <20210218120722.GA14112@dcvr> (raw)
In-Reply-To: <87r1le2bdo.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> Eric Wong writes:
>
> > "maildir:/path/to/dir" has been supported by public-inbox-watch
> > for years, now.
> >
> > The following all work today:
> >
> > lei q -o mboxrd:/tmp/foo.mboxrd ...
> > lei q -o mboxcl2:/tmp/foo.mboxcl2 ...
> > lei q -o maildir:/tmp/foo/ ...
> >
> > So -f/--format seems redundant.
>
> I find "<format>:<destination>" pretty natural/intuitive, even if
> perhaps the stdout case (e.g., "mboxrd:-" or "concatjson:-") looks a bit
> odd. Dropping --format makes sense to me.
How about we just drop --format from the documentation, for now?
(or at least stop recommending it when using with -o)
The stdout case might be a reason to keep it for "lei q",
especially since stdout is the default output:
# this defaults to stdout, looks reasonable:
lei q -f concatjson SEARCH_TERMS...
# this does the same thing, but is more difficult to type and
# looks strange:
lei q -o concatjson:- SEARCH_TERMS
# more readable, but more typing:
lei q -o concatjson:/dev/stdout SEARCH_TERMS
next prev parent reply other threads:[~2021-02-18 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 4:40 does "lei q" --format/-f need to exist? Eric Wong
2021-02-18 5:28 ` Kyle Meyer
2021-02-18 12:07 ` Eric Wong [this message]
2021-02-19 3:10 ` Kyle Meyer
2021-02-19 11:13 ` Eric Wong
2021-02-19 13:47 ` Kyle Meyer
2021-02-19 19:06 ` Eric Wong
2021-02-20 7:12 ` Kyle Meyer
2021-02-20 8:07 ` Eric Wong
2021-02-23 3:45 ` [PATCH] doc: lei: favor "-o format:$PATHNAME" over "-f" Kyle Meyer
2021-02-23 6:03 ` 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=20210218120722.GA14112@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.
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).