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 B9B27431FAF for ; Wed, 22 Aug 2012 17:41:22 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 DNdDmnA9s0tG for ; Wed, 22 Aug 2012 17:41:22 -0700 (PDT) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by olra.theworths.org (Postfix) with ESMTP id 36BC0431FAE for ; Wed, 22 Aug 2012 17:41:22 -0700 (PDT) X-AuditID: 12074422-b7f1f6d00000090b-f3-50357c304223 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 5A.AC.02315.03C75305; Wed, 22 Aug 2012 20:41:20 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q7N0fJvl017362; Wed, 22 Aug 2012 20:41:20 -0400 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q7N0fHkO014904 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 22 Aug 2012 20:41:19 -0400 (EDT) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1T4LU5-0000Ws-5m; Wed, 22 Aug 2012 20:41:17 -0400 Date: Wed, 22 Aug 2012 20:41:17 -0400 From: Austin Clements To: Bart Bunting Subject: Re: Errors after upgrade to 0.14 Message-ID: <20120823004117.GT11179@mit.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkleLIzCtJLcpLzFFi42IRYrdT1zWoMQ0wOLLDyuLinv3sFtdvzmR2 YPJ4tuoWs8epL4fYA5iiuGxSUnMyy1KL9O0SuDKunbvJWvCKu+Lf9oAGxg2cXYycHBICJhK7 D79hh7DFJC7cW8/WxcjFISSwj1Hi6Z8VTCAJIYENjBI3lhRAJE4ySRw8NwmqagmjxOHOTSwg VSwCqhLd606DjWIT0JDYtn85YxcjB4eIgIrEkR18IGFmAWmJb7+bwYYKC2hKHOu5wgpi8wro SLxcs4oZYpmmRMuBq1BxQYmTM5+wQPRqSdz495IJZCTInOX/OEDCnEDhn7dng5WLAm2acnIb 2wRGoVlIumch6Z6F0L2AkXkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrqlebmaJXmpK6SZGcEi7 KO1g/HlQ6RCjAAejEg/vC3PTACHWxLLiytxDjJIcTEqivF8qgEJ8SfkplRmJxRnxRaU5qcWH GCU4mJVEeLuKgHK8KYmVValF+TApaQ4WJXHeayk3/YUE0hNLUrNTUwtSi2CyMhwcShK81dVA jYJFqempFWmZOSUIaSYOTpDhPEDDM0FqeIsLEnOLM9Mh8qcYFaXEeR1AEgIgiYzSPLheWMp5 xSgO9IowbzpIFQ8wXcF1vwIazAQ0WO2qMcjgkkSElFQD46o0ESFGi+XvswJvxuVub4n/n8r/ 2n+vQ/NVxSyBKq0jZ8WU5zbYKPCGFl8NMJPZ83CT6TyTg2qNV44dVFFxlv9rfldXvXaZc03i Lzb+r25Pon4c/mnBe+HdpynH2iY17c9njdLuW++s3nHC+phtyVeX6bLX7Epyd5vtdxWxt323 oNz4cI+DEktxRqKhFnNRcSIA5Q4X0xQDAAA= 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: Thu, 23 Aug 2012 00:41:22 -0000 Quoth Bart Bunting on Aug 23 at 9:36 am: > 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. This is probably "json-readtable-error", which is, unfortunately, about the most generic error the JSON parser can give. > 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. This is definitely not expected behavior. Does this happen when you're searching for messages or when you're viewing a thread? Can you give any more details on what you're doing when you get this error? Try doing M-x toggle-debug-on-error and then triggering the error. Hopefully Emacs will give you a buffer with a backtrace that will give us a better idea of where this is happening.