Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id AB0A36DE025F for ; Tue, 28 Jun 2016 00:57:35 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.011 X-Spam-Level: X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=0.000, 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 EAW_J11RKhgA for ; Tue, 28 Jun 2016 00:57:28 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 6E0646DE00CC for ; Tue, 28 Jun 2016 00:57:07 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1bHnt1-0006Au-V4; Tue, 28 Jun 2016 03:56:48 -0400 Received: (nullmailer pid 10174 invoked by uid 1000); Tue, 28 Jun 2016 07:57:02 -0000 From: David Bremner To: Mark Walters , notmuch@notmuchmail.org Subject: Re: [PATCH] emacs: show: improve handling of mark read tagging errors In-Reply-To: <1465466050-27220-1-git-send-email-markwalters1009@gmail.com> References: <1465336292-18704-1-git-send-email-markwalters1009@gmail.com> <1465466050-27220-1-git-send-email-markwalters1009@gmail.com> User-Agent: Notmuch/0.22+51~gcc1a6d2 (https://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Tue, 28 Jun 2016 09:57:02 +0200 Message-ID: <87r3bh3fw1.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Tue, 28 Jun 2016 07:57:35 -0000 Mark Walters writes: > Previously if a marking read tag change (i.e., removing the unread > tag) failed for some reason, such as a locked database, then no more > mark read tag changes would be attempted in that buffer. > > This handles the error more gracefully. There is not much we can do > yet about dealing with the error itself, and marking read is probably > not important enough to warrant keeping a queue of pending changes or > anything. pushed d