From: Tomi Ollila <tomi.ollila@iki.fi>
To: Tellman <edwint@amazon.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Emacs notmuch-show consistently reports "End of file during parsing"
Date: Thu, 24 May 2012 09:04:32 +0300 [thread overview]
Message-ID: <m2obpew1vz.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20120523183459.GA34543@amazon.com>
On Wed, May 23 2012, Tellman <edwint@amazon.com> 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 <edwint@amazon.com>", "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 <edwint@amazon.com>", "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 <edwint@amazon.com> 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
next prev parent reply other threads:[~2012-05-24 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 14:23 Emacs notmuch-show consistently reports "End of file during parsing" Tellman
2012-05-23 15:25 ` Tomi Ollila
2012-05-23 18:34 ` Tellman
2012-05-24 6:04 ` Tomi Ollila [this message]
2012-05-25 15:53 ` Tellman
2012-05-25 17:03 ` Tomi Ollila
2012-05-25 17:08 ` Tellman, Ed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2obpew1vz.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=edwint@amazon.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).