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 <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