From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: final "null" in "lei q" JSON output
Date: Thu, 11 Mar 2021 22:43:20 +0000 [thread overview]
Message-ID: <20210311224320.GA15581@dcvr> (raw)
The standard JSON (not line-delimited) output is an array with
a "null" element as the last element.
I don't really like it, but it seems necessary if we're
doing parallel writes to stdout and JSON doesn't allow
trailing commas.
So I don't think that part is considered part of the stable
output.
Maybe it could be tweaked to show stats, or something else,
I don't know.
Thoughts?
next reply other threads:[~2021-03-11 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 22:43 Eric Wong [this message]
2021-03-12 4:22 ` final "null" in "lei q" JSON output Kyle Meyer
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=20210311224320.GA15581@dcvr \
--to=e@80x24.org \
--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).