From: Martin Langhoff <martin.langhoff@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>,
Martin Langhoff <martin.langhoff@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Structured (ie: json) output for query commands?
Date: Wed, 30 Jun 2021 19:27:40 -0400 [thread overview]
Message-ID: <CACPiFCLAm+e_JRc=eAt_rqwCWASqr19nXdk0zWqLbTEgELL81w@mail.gmail.com> (raw)
In-Reply-To: <YNzR5ZZDTfcN2Q+s@camp.crustytoothpaste.net>
On Wed, Jun 30, 2021 at 4:20 PM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
> I'm personally fine with the ad-hoc approach we use now, which is
> actually very convenient to script and, in my view, not to terrible to
> parse in other tools and languages. Your mileage may vary, though.
It's of one piece with the Unix tradition that gave us Perl. That's
both a blessing and a curse.
Outputting fields, escapes, etc and the ability to use xpath to
extract, manipulate and query specific data is... very useful. There's
a hard tradeoff with utf-8, and any attempt at papering over that -
iconv conversions, etc – will inevitably munge data in some cases.
hmmm,
m
--
martin.langhoff@gmail.com
- ask interesting questions ~ http://linkedin.com/in/martinlanghoff
- don't be distracted ~ http://github.com/martin-langhoff
by shiny stuff
next prev parent reply other threads:[~2021-06-30 23:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACPiFC++fG-WL8uvTkiydf3wD8TY6dStVpuLcKA9cX_EnwoHGA@mail.gmail.com>
2021-06-30 17:00 ` Structured (ie: json) output for query commands? Martin Langhoff
2021-06-30 17:59 ` Jeff King
2021-06-30 18:20 ` Martin Langhoff
2021-07-01 15:47 ` Jeff King
2021-06-30 20:19 ` brian m. carlson
2021-06-30 23:27 ` Martin Langhoff [this message]
2021-07-01 16:00 ` Jeff King
2021-07-01 21:18 ` brian m. carlson
2021-07-01 21:48 ` Jeff King
2021-07-02 13:13 ` Ævar Arnfjörð Bjarmason
2021-07-01 8:18 ` Han-Wen Nienhuys
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACPiFCLAm+e_JRc=eAt_rqwCWASqr19nXdk0zWqLbTEgELL81w@mail.gmail.com' \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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/mirrors/git.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).