From: Rodney Lorrimar <dev@rodney.id.au>
To: Michael Hudson-Doyle <michael.hudson@canonical.com>,
notmuch@notmuchmail.org
Subject: Re: notmuch-emacs bug report -- infinite looping trying to select next message
Date: Thu, 16 Feb 2012 13:39:01 +0100 [thread overview]
Message-ID: <87ipj7kl5m.fsf@boekje.home> (raw)
In-Reply-To: <87ty2tjcx5.fsf@canonical.com>
Hi Michael,
On Wed, 15 Feb 2012 10:57:42 +1300, Michael Hudson-Doyle <michael.hudson@canonical.com> wrote:
> Thanks for the reply!
>
> On Tue, 14 Feb 2012 10:41:20 +0100, Rodney Lorrimar <dev@rodney.id.au> wrote:
> > Hi Michael,
> >
> > On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle <michael.hudson@canonical.com> wrote:
> > > 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.
> > >
> > > If you load up the thread in emacs, you get a message:
> > >
> > > mm-extern-cache-contents: Couldn't find access type
> >
> > If you put (require 'gnus-art) into your .emacs and eval it, does the
> > problem go away?
>
> No.
Oh well.
I loaded up the thread in notmuch and also got an infinite loop.
> > > Then attempting to advance past the last display message (or pressing A,
> > > or a few other things I expect gets emacs to loop indefinitely.
> > > toggle-debug-on-quit gets me this backtrace:
> >
> > I believe the actual bug is in gnus but I don't really like the loop on
> > error behaviour of notmuch. I would like to try and fix it but haven't
> > found the time.
>
> As far as I can tell, gnus isn't involved here. I may be wrong, of
> course!
After setting a breakpoint in mm-extern-cache-contents I'm inclined to
agree, but I'm not really sure.
The following hack to 0.11 works around the problem. I think the experts
here would be able to come up with something better.
Cheers,
Rodney
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 82d11c9..48c15d2 100644
--- a/emacs/notmuch-show.el
+++ b/emacs/notmuch-show.el
@@ -327,7 +327,8 @@ current buffer, if possible."
(with-temp-buffer
(let ((handle (mm-make-handle (current-buffer) (list content-type))))
(if (and (mm-inlinable-p handle)
- (mm-inlined-p handle))
+ (mm-inlined-p handle)
+ (cdr (mm-handle-type handle)))
(let ((content (notmuch-show-get-bodypart-content msg part nth)))
(insert content)
(set-buffer display-buffer)
next prev parent reply other threads:[~2012-02-16 12:38 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 [this message]
2014-01-24 14:09 ` David Bremner
2014-01-26 20:18 ` Michael Hudson-Doyle
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=87ipj7kl5m.fsf@boekje.home \
--to=dev@rodney.id.au \
--cc=michael.hudson@canonical.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).