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: Fri, 19 Feb 2021 19:06:28 +0000 [thread overview]
Message-ID: <20210219190628.GA1129@dcvr> (raw)
In-Reply-To: <20210219111334.GA25690@dcvr>
Eric Wong <e@80x24.org> wrote:
> Kyle Meyer <kyle@kyleam.com> wrote:
> > Eric Wong writes:
> >
> > > 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:
> > [...]
> >
> > I don't feel strongly one way or the other about keeping --format, but
> > if it is kept around for stdout, I think it'd be good to document it
> > (i.e. your "stop recommending it when using with -o option").
>
> Alright, I think keeping it and only recommending it for stdout
> (or --stdin with import) is the way to go.
>
> "-o format:/path/name" should be encouraged for regular file and
> directory args.
Actually, maybe "-o $format" be implicitly stdout?
(and "-i $format" be implicitly stdin for convert|import)
next prev parent reply other threads:[~2021-02-19 19:06 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 [this message]
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=20210219190628.GA1129@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).