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 0ACB96DE010F for ; Sat, 30 Dec 2017 05:05:47 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5xh1j9N05qWE for ; Sat, 30 Dec 2017 05:05:46 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id E5EFC6DE00DB for ; Sat, 30 Dec 2017 05:05:45 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1eVGpa-0006s0-AQ; Sat, 30 Dec 2017 08:05:42 -0500 Received: (nullmailer pid 1211 invoked by uid 1000); Sat, 30 Dec 2017 13:05:40 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: [PATCH v4 3/3] cli/reply: make --decrypt take a keyword In-Reply-To: <87wp15gmp4.fsf@fifthhorseman.net> References: <20171219164055.20778-1-dkg@fifthhorseman.net> <20171219164055.20778-4-dkg@fifthhorseman.net> <874loha4br.fsf@tethera.net> <87k1x6i560.fsf@fifthhorseman.net> <87zi61zjx3.fsf@tethera.net> <87wp15gmp4.fsf@fifthhorseman.net> Date: Sat, 30 Dec 2017 09:05:40 -0400 Message-ID: <87o9mgz7q3.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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, 30 Dec 2017 13:05:47 -0000 Daniel Kahn Gillmor writes: > It sounds like you were suggesting "--decrypt=nostash" as a synonym for > "--decrypt=true" on show/reply, which i confess i didn't fully > understand when i wrote my response. If it really makes you feel better > to add the alias/synonym, i wouldn't block such a change. Yes, that's what I was suggesting. > But I think the documentation is tricky to write (and trickier to read > and trickier still to understand!) if "--decrypt=nostash" means the > same thing as "--decrypt=true" in one context, but they mean different > things in a different context. I need more time to think about this, so I'd rather defer till after the release in any case. But at some point we collectively (I think? Maybe Jamie and I browbeat you into it) decided that it was OK for --decrypt=true to have context dependent behaviour. It seems to me that "different things in a different context" issue already exists. d