From: Florian Friesdorf <flo@chaoflow.net>
To: Rodney Lorrimar <dev@rodney.id.au>,
Aaron Ecay <aaronecay@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: Infinite loop in emacs interface
Date: Mon, 23 Jan 2012 15:38:04 +0100 [thread overview]
Message-ID: <87aa5eqyb7.fsf@eve.chaoflow.net> (raw)
In-Reply-To: <87d3aaqyur.fsf@eve.chaoflow.net>
On Mon, 23 Jan 2012 15:26:20 +0100, Florian Friesdorf <flo@chaoflow.net> wrote:
> On Tue, 17 Jan 2012 23:44:40 +0100, Rodney Lorrimar <dev@rodney.id.au> wrote:
> >
> > Debugger entered--Lisp error: (void-variable gnus-inhibit-images)
> > mm-shr((#<buffer *temp*> ("text/html") nil nil nil nil nil nil))
> > mm-inline-text-html((#<buffer *temp*> ("text/html") nil nil nil nil nil nil))
> > mm-display-inline((#<buffer *temp*> ("text/html") nil nil nil nil nil nil))
> > mm-display-part((#<buffer *temp*> ("text/html") nil nil nil nil nil nil))
> > notmuch-show-mm-display-part-inline(...snipped...)
> > notmuch-search-show-thread(nil)
> > call-interactively(notmuch-search-show-thread nil nil)
>
> With emacs from git master as of today
> (1f48de2bbf78c87c1dee6425181b31be60d39c7c) and notmuch-0.11 you can
> workaround it:
>
> (require 'gnus-art)
>
> With emacs pretest 24.0.92 there is a bug in gnus.
>
> Fixes/workarounds are discussed in:
> "[PATCH] emacs: Make the part content available to `mm-inline* checks"
sorry, was discussed in:
[RFC][PATCH] emacs: Provide scaffolding so that the new `shr' HTML renderer can run.
--
Florian Friesdorf <flo@chaoflow.net>
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: flo@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
prev parent reply other threads:[~2012-01-23 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 17:17 Infinite loop in emacs interface Rodney Lorrimar
2012-01-17 17:37 ` Aaron Ecay
2012-01-17 18:35 ` Rodney Lorrimar
2012-01-17 22:44 ` Rodney Lorrimar
2012-01-23 14:26 ` Florian Friesdorf
2012-01-23 14:38 ` Florian Friesdorf [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=87aa5eqyb7.fsf@eve.chaoflow.net \
--to=flo@chaoflow.net \
--cc=aaronecay@gmail.com \
--cc=dev@rodney.id.au \
--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).