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 71A41431FAF for ; Wed, 22 Aug 2012 16:36:17 -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 OvKQ1FcnJe2U for ; Wed, 22 Aug 2012 16:36:13 -0700 (PDT) Received: from bit.local (that.urnet.com.au [203.7.149.1]) by olra.theworths.org (Postfix) with ESMTP id 16601431FAE for ; Wed, 22 Aug 2012 16:36:13 -0700 (PDT) Received: by bit.local (Postfix, from userid 501) id 0A8E412AA089; Thu, 23 Aug 2012 09:36:08 +1000 (EST) From: "Bart Bunting" To: notmuch@notmuchmail.org Subject: Errors after upgrade to 0.14 User-Agent: Notmuch/0.13.2+128~g369b28d (http://notmuchmail.org) Emacs/24.2.50.1 (i386-apple-darwin12.0.0) Date: Thu, 23 Aug 2012 09:36:08 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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, 22 Aug 2012 23:36:17 -0000 Good morning, After upgrading to notmuch 014 I am seeing the following messages appear in the messages buffer. error in process filter: byte-code: Wrong type argument: number-or-marker-p, nil error in process filter: Wrong type argument: number-or-marker-p, nil I am also getting a repeating message in the minibuffer (I think) which says something like "json read tail error". Sorry that I am not more specific as I use emacspeak and this message appears to repeat many times interupting speech so I am not 100% sure of what it exactly says. My gut feeling is that it is happening when notmuch is updating the database or something. Is this expected behaviour? It is particularly annoying for me as it sends the speech synth crazy and crashes it for a period of about 30 seconds. If it is expected then I will try and find a way to prevent emacspeak from trying to read it. Kind regards Bart -- Bart Bunting - Engineering Manager - URSYS 459-461 Parramatta Rd. Leichhardt NSW 2040 Australia Ph: +61 2 8745 2811 Mbl: 0409 560 005