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 919A16DE2025 for ; Tue, 28 Feb 2017 17:39:56 -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=[none] 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 KNemPA-4ba1Z for ; Tue, 28 Feb 2017 17:39:55 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTP id D3AE86DE200D for ; Tue, 28 Feb 2017 17:39:55 -0800 (PST) Received: from fifthhorseman.net (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) by che.mayfirst.org (Postfix) with ESMTPSA id A31B7F999; Tue, 28 Feb 2017 20:39:54 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 3D3421FF4F; Tue, 28 Feb 2017 19:17:37 -0500 (EST) From: Daniel Kahn Gillmor To: Steven Allen , notmuch@notmuchmail.org Subject: Re: [RFE] Call `gpg --recv-keys` asynchronously In-Reply-To: <87poi2vyti.fsf@bistromath> References: <87poi2vyti.fsf@bistromath> Date: Tue, 28 Feb 2017 16:17:37 -0800 Message-ID: <87shmxrgta.fsf@alice.fifthhorseman.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, 01 Mar 2017 01:39:56 -0000 On Tue 2017-02-28 12:35:05 -0800, Steven Allen wrote: > Currently, notmuch fetches keys synchronously. This can be *very* slow > (I fetch keys over tor) and locks up emacs for the duration. Therefore, > this fetch really should be asynchronous. > > Unfortunately, getting this to work well (i.e. not interleave output in > the `*notmuch-crypto-gpg-out*` buffer) requires a non-trivial amount of > work. i agree with you that this should be asynchronous, but my elisp-foo isn't sufficient to know how to do this correctly. But i think you've identified a concrete and useful improvement, fwiw. --dkg