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 774B26DE0C51 for ; Sat, 12 Nov 2016 08:15:27 -0800 (PST) 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 2lVF43k22qrS for ; Sat, 12 Nov 2016 08:15:26 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id A078C6DE0AAB for ; Sat, 12 Nov 2016 08:15:26 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1c5axN-0007pf-3u; Sat, 12 Nov 2016 11:15:05 -0500 Received: (nullmailer pid 7382 invoked by uid 1000); Sat, 12 Nov 2016 16:15:23 -0000 From: David Bremner To: Brian Sniffen Cc: Paul Wise , Jani Nikula , notmuch@notmuchmail.org Subject: Re: [PATCH] cli: consider files vanishing during notmuch new non-fatal In-Reply-To: <87h97cu1am.fsf@tethera.net> References: <1478312104.1979.8.camel@debian.org> <1478350621-17137-1-git-send-email-jani@nikula.org> <1478352176.17295.5.camel@debian.org> <87k2c8u2q1.fsf@tethera.net> <60C96E28-48D2-4307-A991-A68469733955@evenmere.org> <87h97cu1am.fsf@tethera.net> Date: Sat, 12 Nov 2016 12:15:23 -0400 Message-ID: <87eg2gu12c.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: Sat, 12 Nov 2016 16:15:27 -0000 David Bremner writes: > Brian Sniffen writes: > >>> >>> OK, but the patch proposed works both for people who want to be notified >>> of this problem, and those that don't (with appropriate shell wrapping >>> checking the return code). >> >> I think it will loop; how do I guarantee termination and indexing of all present messages if deletions cause errors? >> >> -Brian > > stop deleting things? You can't guarantee termination and indexing of > all present messages by ignoring deletions either. > > d Sorry, that was written in haste. Of course if that's your goal ignoring deletions is ok, but renames will still get you, and we have no way of knowing the difference. In any case, I was more thinking that people who want to ignore deletions could check for the specific error code and consider that not-an-error. d