From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc: lei: favor "-o format:$PATHNAME" over "-f"
Date: Tue, 23 Feb 2021 06:03:12 +0000 [thread overview]
Message-ID: <YDSaoBmN35ZlHJZj@dcvr> (raw)
In-Reply-To: <87wnuzsaz3.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> Eric Wong writes:
>
> > Maybe not dropped, but probably tweaked for DWIM-ness.
> >
> > Maybe:
> >
> > If somebody wants a Maildir to dump JSON search results in they
> > could use "-o ./json" or "-o json/" or "-o /path/to/json".
> >
> > "-o json" (no slashes or colons) would mean JSON output to stdout.
> >
> > But then, "json" could be the name of an existing directory,
> > so if it exists...
> >
> > Part of me thinks its too magical...
>
> That's kind of my feeling, though I suspect that would at least
> consistently do what I mean and be unsurprising.
>
> > On the other hand, maybe only requiring the colon: "-o json:"
> > is enough to disambiguate and isn't too much typing.
>
> Yeah, I don't mind that, but I guess that almost gets us back to "-o
> json:-". Then again, I didn't mind that either or really any of the
> options proposed in this thread :)
I'll ponder it more while I work on some other features...
And bash completion still needs to be better in that area.
> Anyway, no matter where this lands, the manpages should switch to
> using/recommending the <format>: prefix, so here's a patch for that.
Yup, thanks, pushed as commit 56b3493c79087979f10f5a3cae7deedaf4ec9fa3
prev parent reply other threads:[~2021-02-23 6:03 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
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 [this message]
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=YDSaoBmN35ZlHJZj@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).