From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: JSON field names in terminal/pager output
Date: Wed, 06 Jan 2021 00:00:21 GMT [thread overview]
Message-ID: <878s97ylws.fsf@kyleam.com> (raw)
In-Reply-To: <20210105095646.GA26897@dcvr>
Eric Wong writes:
> Are "f", "s", "t", "c" acceptable field names to show in JSON
> output? (instead of from/subject/to/cc)
In my view they are, and, as you mention next, I like that they align
with the search prefixes.
> Anyways, the current JSON output looks something like the
> following, comments inline
>
> [{
[...]
Nice.
> "references": [
> "<20210105090437.22801-1-e@80x24.org>",
> "<20210105090437.22801-5-e@80x24.org>"
> ],
>
> # we don't actually support searching on rereference, yet;
> # not sure if it's needed since we already do thread # expansion
Is "thread # expansion" the "num -> tid -> nums" mapping done by Over's
expand_thread()? And, from the CLI, that will be triggered by
`thread|t', right?
next prev parent reply other threads:[~2021-01-06 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 9:56 JSON field names in terminal/pager output Eric Wong
2021-01-06 0:00 ` Kyle Meyer [this message]
2021-01-06 10:27 ` 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=878s97ylws.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=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.
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).