From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 5F8611F9FD;
	Thu,  4 Mar 2021 18:43:48 +0000 (UTC)
Date: Thu, 4 Mar 2021 18:43:48 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: angle brackets in "m:" and "refs:" in "lei q" JSON
Message-ID: <20210304184348.GA19350@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

I'm thinking these shouldn't include angle brackets:

  "m": "<20210228122528.18552-2-e@80x24.org>",
  "refs": ["<20210228122528.18552-1-e@80x24.org>"],

Using angle brackets on the command-line requires quoting to
disambiguate against redirects, so it's a pain.  Leaving the
brackets in still works because of how Xapian's query parser
works, not because of anything we do on our end.

Since the actual headers are "Message-ID" and "References", (and
not "m" or "refs"), I think it's clear that we don't have to
match the raw mail contents exactly.  We RFC 2047 decode
"f|t|c|s" fields anyways instead of showing the raw values,
so more precedence for leaving out <>.