unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	21650@debbugs.gnu.org, Mike Kupfer <m.kupfer@acm.org>
Subject: bug#21650: fix should be underneath MH-E
Date: Tue, 02 Feb 2016 21:58:53 -0800	[thread overview]
Message-ID: <79498.1454479133@olgas.newt.com> (raw)
In-Reply-To: <b4mh9hqkb08.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> wrote:

> On Tue, 02 Feb 2016 13:28:47 -0500, Glenn Morris wrote:
> > Mike Kupfer wrote:
> 
> >> But MIME libraries are documented as general-purpose, rather than
> >> private to Gnus. So this really ought to be resolved at the mm layer,
> >> rather than adding renderer-specific tweaks to MH-E.
> 
> > Sounds absolutely right.
> 
> The first step should be anyway to fix mh-cl-flet[1], recompile
> mh-e, and see how the behaviors change, I think.
> 
> [1] <http://article.gmane.org/gmane.emacs.bugs/111280>

By the way, I've made your suggested mh-cl-flet fix to MH-E (thanks!!!)
and am letting it bake. I'll try to make some time to check it in this
weekend since I haven't noticed any ill effects.

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD





  parent reply	other threads:[~2016-02-03  5:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 17:03 bug#21650: 24.5; mh-e keeps trying to open urls Simon Gerraty
2015-10-08 19:20 ` Eli Zaretskii
2015-10-08 20:19   ` Simon J. Gerraty
2015-10-08 21:21     ` Glenn Morris
2015-10-09 15:10       ` Simon J. Gerraty
2015-10-09  7:11     ` Eli Zaretskii
2015-12-23  6:07       ` Bill Wohler
2016-01-09  2:20         ` Mike Kupfer
2015-10-09  1:23 ` Wolfgang Jenkner
2016-02-01 18:53 ` bug#21650: fix should be underneath MH-E Mike Kupfer
2016-02-02 18:28   ` Glenn Morris
2016-02-02 22:23     ` Katsumi Yamaoka
2016-02-02 22:34       ` Glenn Morris
2016-02-02 23:34         ` Katsumi Yamaoka
2016-02-03  2:31         ` Lars Ingebrigtsen
2016-02-03  9:43           ` Katsumi Yamaoka
2016-02-03 22:52             ` Bill Wohler
2016-02-04  3:58               ` Mike Kupfer
2016-02-03  5:58       ` Bill Wohler [this message]
2016-02-04  6:09 ` Katsumi Yamaoka
2016-02-05  1:41   ` Mike Kupfer
2016-02-05  6:04 ` Katsumi Yamaoka
2016-02-06 22:53   ` Mike Kupfer
2016-02-05  6:41 ` Katsumi Yamaoka
2016-02-08 22:43 ` Katsumi Yamaoka
2016-02-09  0:41   ` Mike Kupfer
2016-02-09  3:24     ` Mike Kupfer
2016-02-09  1:49 ` Katsumi Yamaoka
2016-02-09  4:41 ` Katsumi Yamaoka
2016-02-09  5:49   ` Bill Wohler
2016-02-09 15:17   ` Mike Kupfer
2016-02-09 22:15 ` Katsumi Yamaoka
2016-02-10  2:23   ` Mike Kupfer
2016-02-10  3:51     ` Bill Wohler
2016-02-28  3:20     ` Mike Kupfer
2016-06-07  0:35 ` bug#21650: 21650: fixed in Emacs 25 Mike Kupfer

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79498.1454479133@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=21650@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=m.kupfer@acm.org \
    --cc=yamaoka@jpl.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://git.savannah.gnu.org/cgit/emacs.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).