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 3C0C06DE01F7 for ; Sun, 5 Jun 2016 05:34:25 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.012 X-Spam-Level: X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 pN13_qA7JAIM for ; Sun, 5 Jun 2016 05:34:17 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 6EE646DE01D0 for ; Sun, 5 Jun 2016 05:34:17 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1b9XFk-0005zv-1r; Sun, 05 Jun 2016 08:34:04 -0400 Received: (nullmailer pid 10585 invoked by uid 1000); Sun, 05 Jun 2016 12:34:13 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: notmuch restore --include=config --accumulate User-Agent: Notmuch/0.22+28~gb9bf3f4 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sun, 05 Jun 2016 09:34:13 -0300 Message-ID: <87lh2jddbu.fsf@zancas.localnet> 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: Sun, 05 Jun 2016 12:34:25 -0000 Recently notmuch-restore gained the option to restore configuration information (--include=config). One potentially surprising aspect is that it behaves as if --accumulate was given for config data, even if replacing all the tags on each message. To be precise, if some config data is in the database, and not mentioned in the input to restore, it will still be there afterwards. I lean towards this being a feature rather than a bug, since I think it would be even more surprising to have the config data wiped out. I guess not many people use this feature yet (or even know about it), so we can still change this behaviour. Or at least document it better. A lawyerly reading of the docs is consistent with the current behaviour, but it is a bit misleading (as with all good lawyerly things). d