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 5DF646DE00C4 for ; Fri, 7 Sep 2018 04:31:30 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.395 X-Spam-Level: X-Spam-Status: No, score=0.395 tagged_above=-999 required=5 tests=[AWL=-0.238, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=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 dHAqrbNSwfcf for ; Fri, 7 Sep 2018 04:31:29 -0700 (PDT) Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by arlo.cworth.org (Postfix) with ESMTPS id 714926DE00AC for ; Fri, 7 Sep 2018 04:31:29 -0700 (PDT) Received: by mail-wm0-f50.google.com with SMTP id 207-v6so14213085wme.5 for ; Fri, 07 Sep 2018 04:31:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:subject:in-reply-to:references:from:date:message-id:mime-version :content-transfer-encoding; bh=mldjbRx/gzX7P0D2Ks0bWoIOp8T3J+14IJfLikiXZHA=; b=GPlq3bQmVeLSHz5iEa7oi3POdV5oWfMtu2L1TF8/ESi3SORA/yRkPQ78YysWw5mycg ArEK+Nx0XOo5xAFReeA2EKyLHD6/bl4RVNJP8dbZahh02oMMlf04A1/pGCgN9uEqqLuR Tki+Kk1IVfp3CCa67fEinzd51D1BrkFrZ/roIXH09Eak8dcZ77LRlWAMjJHe0gye9gIZ EYPvCkpQQBs82bbvYIIe5UyGOteEwG5m6qceGD5HPyJJHznR26O6uR2JDUIEdhfN3WfY 0dSIU6Y7FA03VInIa+WedeEXtw1qyxrh/r9/3wFUEqq1jpPyNl7MK2PWM26c5Hzzm48p Hj9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version:content-transfer-encoding; bh=mldjbRx/gzX7P0D2Ks0bWoIOp8T3J+14IJfLikiXZHA=; b=o3MgTmeAdEIV1TNCX56f5Ll8gTo1L3a/kvpco/+SXv+ot87OWg8YWPC7Q1XqLjIl2y lpWs6bV3vE6gBW6fsBDRsMUWj8ybIUxdl1oO8lSzuPRDVb1mz4ipDJnfKmI0nfScTGpH IQI0XnFezrGyccXd4lbpyECixKgQdd6ed8N6lFwN7IY32WKJUP9WNkIbI9bJ29dyUZ3s HByRghJ+HHxzDpB6PTj1H+WN93nKMnY33/gTlmKQGz41IYyYjYU7lvCHnvoxyh9OLYgK TdezauiOF5z9f7EZ/Xq18enPh4qrgk+385O5leMvJxHY0ug8YOYVm3Gzp4CqHTJ9zZGs XmrA== X-Gm-Message-State: APzg51Di0rG5LRVNu6rWshfe+tt9iVl9vZfLlM8npDJFpkx6zefM7Pnz zjGgKSuiTmXFtP7TDriviiVDtHl7Prw= X-Google-Smtp-Source: ANB0VdadJCYiUkpkbNqnyH+RI9Sv9BcJjJaPVgyQoPwZiHPlbGGZj26mYJvY5RhTyivPgW/eK8i81g== X-Received: by 2002:a1c:752:: with SMTP id 79-v6mr5162577wmh.59.1536319888072; Fri, 07 Sep 2018 04:31:28 -0700 (PDT) Received: from disaster-area.hh.sledj.net (disaster-area.hh.sledj.net. [81.149.164.25]) by smtp.gmail.com with ESMTPSA id z10-v6sm9039451wrv.22.2018.09.07.04.31.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Sep 2018 04:31:26 -0700 (PDT) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 8bc0e0a3; Fri, 7 Sep 2018 11:31:26 +0000 (UTC) To: Antoine =?utf-8?Q?Beaupr=C3=A9?= , notmuch@notmuchmail.org Subject: Re: feature request: fetch missing keys in the background In-Reply-To: <87bm9duzbj.fsf@curie.anarc.at> References: <871saawphm.fsf@curie.anarc.at> <87va7mv75u.fsf@curie.anarc.at> <87pnxuuzt6.fsf@curie.anarc.at> <87efe9v12t.fsf@curie.anarc.at> <87bm9duzbj.fsf@curie.anarc.at> X-HGTTG: constant-mown From: David Edmondson Date: Fri, 07 Sep 2018 12:31:26 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 07 Sep 2018 11:31:30 -0000 On Tuesday, 2018-09-04 at 10:12:00 -04, Antoine Beaupr=C3=A9 wrote: > So I tried that and it works, if I really don't touch anything. It's > certainly an improvement over the previous behavior. Once the "message" > is gone (ie. as soon as anything else is done in Emacs), it's a little > hard to figure out what is happening without going through the status > buffer. > > Maybe that's fine, but it would be nice if the button would immediately > update with that status. For example, the text could change to > "... updating" or something. Of course, we're back to the same place > that it can't be updated without shuffling the buffer around if the > point moved, but at least the UI would "remember" there was some change > in the status (it's not just "Failure" but "We're working on it"). v2 of the patch does this. dme. --=20 When I grow up I'll be stable.