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 43CEC6DE115F for ; Wed, 2 Nov 2016 04:04:42 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.006 X-Spam-Level: X-Spam-Status: No, score=-0.006 tagged_above=-999 required=5 tests=[AWL=0.005, 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 fZokMLi3G3Ty for ; Wed, 2 Nov 2016 04:04:41 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 94F3D6DE1149 for ; Wed, 2 Nov 2016 04:04:41 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1c1tLC-0007uo-FD; Wed, 02 Nov 2016 07:04:22 -0400 Received: (nullmailer pid 23198 invoked by uid 1000); Wed, 02 Nov 2016 11:04:38 -0000 From: David Bremner To: Mark Walters , notmuch@notmuchmail.org Subject: Re: [PATCH 1/2] emacs: tree: allow the user to decrypt the message pane In-Reply-To: <1474472959-8739-1-git-send-email-markwalters1009@gmail.com> References: <1474472959-8739-1-git-send-email-markwalters1009@gmail.com> Date: Wed, 02 Nov 2016 08:04:38 -0300 Message-ID: <87shrarvll.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Wed, 02 Nov 2016 11:04:42 -0000 Mark Walters writes: > This makes $ in the tree pane toggle decryption in the message > pane. Without this the user can only decrypt the message pane by > switching to it, or by setting decryption on globally by setting > notmuch-crypto-process-mime to t. > --- > > This seems an obvious extension. It may not be very useful as most > people who get encrypted messages probably set > notmuch-crypto-process-mime to t. > pushed to master. > As an aside might it be worth making that the default > (notmuch-crypto-process-mime equal to t)? that works fine for my use case, I guess the question is how many people use a setup where they have access to secret key material only on one machine. Also not sure what happens to people using notmuch remotely d