From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id AC5DC6DE0931 for ; Thu, 3 May 2018 19:26:33 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.514 X-Spam-Level: X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=-2.514, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jVGuAqkZ3xDl for ; Thu, 3 May 2018 19:26:32 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTPS id 3B3BC6DE0352 for ; Thu, 3 May 2018 19:26:32 -0700 (PDT) Received: from fifthhorseman.net (unknown [IPv6:2001:470:1f07:60d:d6:baff:fec7:6cfa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 06311F99A for ; Thu, 3 May 2018 22:26:28 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id 3D13E2042E; Thu, 3 May 2018 22:26:24 -0400 (EDT) From: Daniel Kahn Gillmor To: Notmuch Mail Subject: match: in structured "notmuch reply" output Date: Thu, 03 May 2018 22:26:24 -0400 Message-ID: <87vac4nokv.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 02:26:33 -0000 hey good notmuch people. I noticed today that "notmuch reply --format=json id:foo@example.net" emits a json object that contains: "match": false, reading devel/schemata, it looks like this is kind of a vestigial thing from "notmuch show" and it doesn't really belong in "notmuch reply". bremner points out on IRC that removing this element would be a backward-incompatible change for the schema. we could also change its output to true (since presumably it does match the requested e-mail). or, we could just ignore the issue and try to remember to rip it out next time we change the output format, as i think every consumer of structured "notmuch reply" output already probably ignores this flag. if you're working on a consumer of "notmuch reply" structured output, does this flag mean anything to you? does it need to stick around, or does its value mean something one way or another? --dkg