unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: notmuch-emacs bug report -- infinite looping trying to select next message
Date: Mon, 27 Jan 2014 09:18:08 +1300	[thread overview]
Message-ID: <871tzuzedb.fsf@canonical.com> (raw)
In-Reply-To: <87eh3xpj3i.fsf@zancas.localnet>

David Bremner <david@tethera.net> writes:

> Michael Hudson-Doyle <michael.hudson@canonical.com> writes:
>
>> The attached gzipped mbox appears to trip up the emacs interface.  The
>> problem seems to come from the message with id
>> CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2cK+A@mail.gmail.com.
>>
>
> I can't reproduce this bug in current git, so I'm going to assume
> something fixed it in the intervening years.

I find the same.

> In particular our handling of error reporting for corrupted parts
> changed, so maybe that was it.

When I load up the thread that caused the problem I end up with this in
the buffer:

         [ message/external-body ]
         !!! Bodypart insert error: Couldn't find access type !!!
         [ text/plain ]

so I think it's pretty likely your guess is accurate.

> Thanks so much for including a test case with your bug report,

No problem, thanks for checking this ancient report!  (And thanks to
myself for including the message-id in the report...)

Cheers,
mwh

      reply	other threads:[~2014-01-26 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 22:01 notmuch-emacs bug report -- infinite looping trying to select next message Michael Hudson-Doyle
2012-02-14  9:41 ` Rodney Lorrimar
2012-02-14 21:57   ` Michael Hudson-Doyle
2012-02-16 12:39     ` Rodney Lorrimar
2014-01-24 14:09 ` David Bremner
2014-01-26 20:18   ` Michael Hudson-Doyle [this message]

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=871tzuzedb.fsf@canonical.com \
    --to=michael.hudson@canonical.com \
    --cc=david@tethera.net \
    --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).