From b308b2bc0df86161713f3e7dcdd1458750430ed4 Mon Sep 17 00:00:00 2001 From: Tellman Date: Sat, 26 May 2012 08:53:31 +1700 Subject: [PATCH] Re: Emacs notmuch-show consistently reports "End of file during parsing" --- 7d/3bf493c4d2ed36586b607f5ba2e308c201ba30 | 146 ++++++++++++++++++++++ 1 file changed, 146 insertions(+) create mode 100644 7d/3bf493c4d2ed36586b607f5ba2e308c201ba30 diff --git a/7d/3bf493c4d2ed36586b607f5ba2e308c201ba30 b/7d/3bf493c4d2ed36586b607f5ba2e308c201ba30 new file mode 100644 index 000000000..8487f3693 --- /dev/null +++ b/7d/3bf493c4d2ed36586b607f5ba2e308c201ba30 @@ -0,0 +1,146 @@ +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 0BF09431FBC + for ; Fri, 25 May 2012 08:53:35 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 1.842 +X-Spam-Level: * +X-Spam-Status: No, score=1.842 tagged_above=-999 required=5 + tests=[DKIM_ADSP_ALL=1.1, NO_DNS_FOR_FROM=0.379, RDNS_DYNAMIC=0.363] + 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 N5UxhhrOnvbG for ; + Fri, 25 May 2012 08:53:34 -0700 (PDT) +Received: from 78ca391a1b82.ant.amazon.com (207-171-191-60.amazon.com + [207.171.191.60]) + by olra.theworths.org (Postfix) with ESMTP id 5CD86431FB6 + for ; Fri, 25 May 2012 08:53:34 -0700 (PDT) +Received: by 78ca391a1b82.ant.amazon.com (Postfix, from userid 1829422907) + id DAB4CDE7F19; Fri, 25 May 2012 08:53:32 -0700 (PDT) +Date: Fri, 25 May 2012 08:53:31 -0700 +From: Tellman +To: Tomi Ollila +Subject: Re: Emacs notmuch-show consistently reports "End of file during + parsing" +Message-ID: <20120525155331.GA80819@amazon.com> +References: <20120523142301.GC10576@amazon.com> + + <20120523183459.GA34543@amazon.com> + +Mime-Version: 1.0 +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +In-Reply-To: +User-Agent: Mutt/1.4.2.3i +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 15:53:35 -0000 + +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. + +Thanks for your help. + +--Ed + +On Wed, May 23, 2012 at 11:04:32PM -0700, Tomi Ollila wrote: +> On Wed, May 23 2012, Tellman wrote: +> +> > Thanks for the quick response. +> > +> > I have gmime 2.4 installed. +> +> Gmime 2.4.x -- what is the value if 'x' :D ? +> +> > 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. +> +> > Here's a sample: +> > +> > (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"}]}, []]]]78ca391a1b82:gmime +> > +> > I tried a bunch of other ones, and they all looked similar. +> +> +> 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"}]}, []]]] +> +> ...... the message OK... You could next try to enter +> +> id:"5qt490ipfnbu1z.fsf@78ca391a1b82.ant.amazon.com" +> +> into your notmuch-hello search bar and see if that message shows ok. +> +> If that does then just some threads makes the parsing fail. +> +> 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. +> +> > +> > Thanks, +> > --Ed +> +> Tomi +> +> > +> > +> > On Wed, May 23, 2012 at 08:25:26AM -0700, Tomi Ollila wrote: +> >> On Wed, May 23 2012, Tellman wrote: +> >> +> >> > 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. +> >> +> >> > 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. +> >> +> >> > 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? +> >> +> >> What version of gmime is installed ? +> >> +> >> Do the following on command line (the l33t... below is +> >> actually a date 'Tue May 15 23:10:56 2012 UTC'). +> >> +> >> notmuch search --output=threads 1337123456.. +> >> +> >> and then execute +> >> +> >> notmuch show --format=json thread:000000000000XXXX +> >> +> >> (take the XXX from the thread list outputted before +> >> -- try many of those and see whether something fails +> >> during execution...). +> >> +> >> > Thanks, +> >> > --Ed Tellman +> >> +> >> Tomi +> > _______________________________________________ +> > notmuch mailing list +> > notmuch@notmuchmail.org +> > http://notmuchmail.org/mailman/listinfo/notmuch -- 2.26.2