unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] Fix gnus-inhibit-images bug in Emacs 24
Date: Sat, 29 Sep 2012 23:26:35 +0300	[thread overview]
Message-ID: <m2d3141sp0.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1348941314-8377-1-git-send-email-amdragon@mit.edu>

On Sat, Sep 29 2012, Austin Clements <amdragon@MIT.EDU> wrote:

> This series adds a test for the gnus-inhibit-images bug and then
> provides one possile work-around.
>
> Another possible approach is to advise mm-shr to load gnus-art.  That
> might be a better approach, given that mm-shr is the only function
> outside of gnus-art itself that references gnus-inhibit-images.

LGTM. My vote goes for patches (i.e. I like the advice approach).

id:"1348941314-8377-2-git-send-email-amdragon@mit.edu"
id:"1348941314-8377-3-git-send-email-amdragon@mit.edu"
id:"1348941823-15516-1-git-send-email-amdragon@mit.edu"

Tomi


>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  parent reply	other threads:[~2012-09-29 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 17:55 [PATCH 0/3] Fix gnus-inhibit-images bug in Emacs 24 Austin Clements
2012-09-29 17:55 ` [PATCH 1/3] test: Clear test-ouput output file before running Emacs tests Austin Clements
2012-09-29 17:55 ` [PATCH 2/3] test: Add a test for HTML email with inline images Austin Clements
2012-10-03  9:35   ` Dmitry Kurochkin
2012-10-03 14:28     ` Austin Clements
2012-10-03 14:41       ` Dmitry Kurochkin
2012-09-29 17:55 ` [PATCH 3/3] emacs: Work around gnus-inhibit-images bug in mm-shr Austin Clements
2012-09-29 18:03   ` [PATCH] " Austin Clements
2012-09-29 20:26 ` Tomi Ollila [this message]
2012-10-01  2:38   ` [PATCH 0/3] Fix gnus-inhibit-images bug in Emacs 24 David Bremner

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=m2d3141sp0.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=amdragon@MIT.EDU \
    --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).