Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id E654A431FBF for ; Sat, 12 Jul 2014 12:09:09 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.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 olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zvehlc457CU for ; Sat, 12 Jul 2014 12:09:05 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 364E4431FBD for ; Sat, 12 Jul 2014 12:09:05 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1X62fN-0003R3-EM; Sat, 12 Jul 2014 16:09:01 -0300 Received: (nullmailer pid 21659 invoked by uid 1000); Sat, 12 Jul 2014 19:08:57 -0000 From: David Bremner To: Austin Clements , David Edmondson Subject: Re: Add support for specifying tags during "notmuch new" In-Reply-To: <20140502151800.GC8365@mit.edu> References: <1399018555-1994-1-git-send-email-dme@dme.org> <20140502151800.GC8365@mit.edu> User-Agent: Notmuch/0.18.1+22~gbf82697 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 12 Jul 2014 16:08:57 -0300 Message-ID: <87a98ev1h2.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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 Jul 2014 19:09:10 -0000 Austin Clements writes: > What happens when this script dies in the middle (say, your computer > loses power or notmuch tag conflicts with something else on the write > lock)? One advantage of the standard "new" tag approach is that it's > easy to write a stateless post-new tagging script that can be killed > at any point and restarted. (You're right that post-new has a > concurrency issue, but we should fix that in its own right.) Hi David, Hi Austin; So, what to do about this patch series? Is it actually a bad idea to allow specifying tags for notmuch new? We already allow it via config, right, so this just makes things more convenient. d