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 5FA39431FBC for ; Fri, 25 May 2012 10:08:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -9.9 X-Spam-Level: X-Spam-Status: No, score=-9.9 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, USER_IN_DEF_DKIM_WL=-7.5] 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 PoBydgEZMKfE for ; Fri, 25 May 2012 10:08:17 -0700 (PDT) Received: from smtp-fw-31001.amazon.com (smtp-fw-31001.amazon.com [207.171.178.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 91C5D431FB6 for ; Fri, 25 May 2012 10:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=edwint@amazon.com; q=dns/txt; s=rte02; t=1337965697; x=1369501697; h=from:to:cc:date:subject:message-id:in-reply-to: content-transfer-encoding:mime-version; bh=RzXj+x3nVhI5ffkoB6N5EPskRtOovtcxyontZmmpVcU=; b=ijwrSX+pcp+fmV/6hBQwp6bzZDxrII5ztFghrG6Qgo6U//INTUqy369m ZvAv3FYrZx0VTrWiWcHMmJllPN3L0Q==; X-IronPort-AV: E=Sophos;i="4.75,658,1330905600"; d="scan'208";a="238479837" Received: from smtp-in-9003.sea19.amazon.com ([10.186.104.20]) by smtp-border-fw-out-31001.sea31.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 May 2012 17:08:15 +0000 Received: from ex-hub-9001.ant.amazon.com (ex-hub-9001.sea19.amazon.com [10.185.10.26]) by smtp-in-9003.sea19.amazon.com (8.13.8/8.13.8) with ESMTP id q4PH8FiF002345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 25 May 2012 17:08:15 GMT Received: from ex-sea19-a.ant.amazon.com ([fe80::d0e0:1192:9ab:523d]) by ex-hub-9001.ant.amazon.com ([fe80::e043:4e29:5b93:e34b%12]) with mapi; Fri, 25 May 2012 10:08:12 -0700 From: "Tellman, Ed" To: Tomi Ollila Date: Fri, 25 May 2012 10:08:11 -0700 Subject: Re: Emacs notmuch-show consistently reports "End of file during parsing" Thread-Topic: Emacs notmuch-show consistently reports "End of file during parsing" Thread-Index: Ac06mPdyKRXin9PiRKeqG6g6uWLffQ== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Fri, 25 May 2012 17:08:20 -0000 Unfortunately, I didn't check before I replaced it. I just removed the one from mac-ports, got the most recent 2.4 version and compiled it from source. I also installed notmuch 0.12 instead of 0.11, so that may have been what fixed things. Sorry, I didn't do it more systematically to help identify the actual problem. --Ed On 5/25/12 10:03 AM, "Tomi Ollila" wrote: >On Fri, May 25 2012, Tellman wrote: > >> I installed gmime 2.4.28 and notmuch 0.12 and that combination seems to >> work fine. >> >> I'm not sure what the problem was, but it seems OK now. > >Good that it works for you! > >Do you happen to know which version of gmime you were using previously -- >http://www.macports.org/ports.php?by=3Dlibrary&substr=3Dgmime shows versio= n >2.4.23 (but that is just something that internet search presented me) > >> Thanks for your help. >> >> --Ed > >Tomi > > >> >> On Wed, May 23, 2012 at 11:04:32PM -0700, Tomi Ollila wrote: >>> On Wed, May 23 2012, Tellman wrote: >>>=20 >>> > Thanks for the quick response. >>> > >>> > I have gmime 2.4 installed. >>>=20 >>> Gmime 2.4.x -- what is the value if 'x' :D ? >>>=20 >>> > I tried the search and show commands and the responses all looked OK >>>to >>> > me, although I wasn't quite sure what to look for. I didn't see any >>> > error messages. >>>=20 >>> > Here's a sample: >>> > >>> > (json-read)[[[{"id": >>>"5qt490ipfnbu1z.fsf@78ca391a1b82.ant.amazon.com", "match": true, >>>"filename":=20 >>>"/Users/edwint/mail/INBOX/sent/cur/1337734168.4985_755109_1.78ca391a1b82 >>>.ant.amazon.com:2,S", "timestamp": 1337734168, "date_relative": "Yest. >>>17:49", "tags": ["inbox"], "headers": {"Subject": "hi", "From": "Ed >>>Tellman ", "To": "edwint@amazon.com", "Cc": "", >>>"Bcc": "", "Date": "Tue, 22 May 2012 17:49:28 -0700"}, "body": [{"id": >>>1, "content-type": "text/plain", "content": "hi\n"}]}, >>>[]]]]78ca391a1b82:gmime >>> > >>> > I tried a bunch of other ones, and they all looked similar. >>>=20 >>>=20 >>> Putting cursor /here (use monospace font ;) and entering C-x C-e >>>parses ...... >>> | >>> | >>> V >>> (json-read)[[[{"id": "5qt490ipfnbu1z.fsf@78ca391a1b82.ant.amazon.com", >>>"match": true, "filename": >>>"/Users/edwint/mail/INBOX/sent/cur/1337734168.4985_755109_1.78ca391a1b82 >>>.ant.amazon.com:2,S", "timestamp": 1337734168, "date_relative": "Yest. >>>17:49", "tags": ["inbox"], "headers": {"Subject": "hi", "From": "Ed >>>Tellman ", "To": "edwint@amazon.com", "Cc": "", >>>"Bcc": "", "Date": "Tue, 22 May 2012 17:49:28 -0700"}, "body": [{"id": >>>1, "content-type": "text/plain", "content": "hi\n"}]}, []]]] >>>=20 >>> ...... the message OK... You could next try to enter >>>=20 >>> id:"5qt490ipfnbu1z.fsf@78ca391a1b82.ant.amazon.com" >>>=20 >>> into your notmuch-hello search bar and see if that message shows ok. >>>=20 >>> If that does then just some threads makes the parsing fail. >>>=20 >>> I have had similar experience: when using gmime 2.4.21 some threads >>> (note: not all) make notmuch segfault. Updating to 2.4.25 fixed that >>> problem. You may have the same problem or not. >>>=20 >>> > >>> > Thanks, >>> > --Ed >>>=20 >>> Tomi >>>=20 >>> > >>> > >>> > On Wed, May 23, 2012 at 08:25:26AM -0700, Tomi Ollila wrote: >>> >> On Wed, May 23 2012, Tellman wrote: >>> >>=20 >>> >> > I recently installed notmuch on my OS X laptop. Searching works >>>fine--it >>> >> > seems to find all my mail and displays the subject lines, dates, >>>etc., >>> >> > correctly. >>> >>=20 >>> >> > However, the emacs mode is unable to display the contents of any >>>of the >>> >> > messages. I see the subjects correctly, but when I try to view >>>the >>> >> > actual message, I see: "End of file during parsing" and an empty >>>page. >>> >>=20 >>> >> > I have OS X Lion, Emacs.App, version 23.2.1, and notmuch version >>>0.11 >>> >> > installed via MacPorts. >>> >> > >>> >> > Does anyone have an idea what might be causing this? >>> >>=20 >>> >> What version of gmime is installed ? >>> >>=20 >>> >> Do the following on command line (the l33t... below is >>> >> actually a date 'Tue May 15 23:10:56 2012 UTC'). >>> >>=20 >>> >> notmuch search --output=3Dthreads 1337123456.. >>> >>=20 >>> >> and then execute >>> >>=20 >>> >> notmuch show --format=3Djson thread:000000000000XXXX >>> >>=20 >>> >> (take the XXX from the thread list outputted before >>> >> -- try many of those and see whether something fails >>> >> during execution...). >>> >>=20 >>> >> > Thanks, >>> >> > --Ed Tellman >>> >>=20 >>> >> Tomi >>> > _______________________________________________ >>> > notmuch mailing list >>> > notmuch@notmuchmail.org >>> > http://notmuchmail.org/mailman/listinfo/notmuch >> _______________________________________________ >> notmuch mailing list >> notmuch@notmuchmail.org >> http://notmuchmail.org/mailman/listinfo/notmuch