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 19EB76DE0F56 for ; Fri, 24 May 2019 18:36:06 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.04 X-Spam-Level: X-Spam-Status: No, score=-0.04 tagged_above=-999 required=5 tests=[AWL=-0.039, SPF_PASS=-0.001] 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 DASHAD0X0hsp for ; Fri, 24 May 2019 18:36:05 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 81E996DE0F51 for ; Fri, 24 May 2019 18:36:05 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hULbQ-0007zL-6T; Fri, 24 May 2019 21:36:04 -0400 Received: (nullmailer pid 31975 invoked by uid 1000); Sat, 25 May 2019 01:36:10 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: [PATCH v2 4/4] cli/show: emit new whole-message crypto status output In-Reply-To: <878suv5vbz.fsf@fifthhorseman.net> References: <20190520032228.27420-1-dkg@fifthhorseman.net> <20190520032228.27420-5-dkg@fifthhorseman.net> <87mujdsav0.fsf@tethera.net> <87ef4n62d9.fsf@fifthhorseman.net> <878suv5vbz.fsf@fifthhorseman.net> Date: Fri, 24 May 2019 22:36:10 -0300 Message-ID: <87a7fbnwmt.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Sat, 25 May 2019 01:36:06 -0000 Daniel Kahn Gillmor writes: > > or, should we just make the crypto member always present? > That was what I was thinking, sorry to be less explicit than I could have been. > Another alternative is to condition the presence of the crypto member on > the arguments (like if --verify is set), but the decision for --decrypt > is a bit awkward because of our default of --decrypt=auto. >