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 018CA431FB6 for ; Wed, 2 Jul 2014 10:38:19 -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 U4FwkwokHd8S for ; Wed, 2 Jul 2014 10:38:15 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by olra.theworths.org (Postfix) with ESMTP id 78BB0431FAF for ; Wed, 2 Jul 2014 10:38:15 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id A1EFE100033; Wed, 2 Jul 2014 20:38:03 +0300 (EEST) From: Tomi Ollila To: =?utf-8?Q?Nicol=C3=A1s?= Reynolds , notmuch@notmuchmail.org Subject: Re: queuing database tasks? In-Reply-To: <87y4wcll92.fsf@endefensadelsl.org> References: <87y4wcll92.fsf@endefensadelsl.org> User-Agent: Notmuch/0.18.1+25~gdaf4b6f (http://notmuchmail.org) Emacs/24.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ 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.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: Wed, 02 Jul 2014 17:38:19 -0000 On Wed, Jul 02 2014, Nicol=C3=A1s Reynolds wrote: > hi! sometimes my machine takes a little while to process new emails and > if i'm reading email during that moment, tagging and untagging fails > because the xapian database is write locked. > > this affects manual tagging but also the emacs interface removing the > unread tag so i often have to come back or wait to do it manually. > > would it be possible to queue these actions until the database is > unlocked again or any other solution? It would. SMOP. Especially when done properly. I.e. patches tolerated... ... it might be beneficial to first have some discussions on the matter, but if one impress us with good set of patches that is always a big plus. > > --=20 > :{ Tomi