From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17146@debbugs.gnu.org, nbtrap@nbtrap.com
Subject: bug#17146: 24.4.50; File save with incapable coding system precluded by strange error message
Date: Mon, 31 Mar 2014 18:54:24 +0300 [thread overview]
Message-ID: <83ha6ecqj3.fsf@gnu.org> (raw)
In-Reply-To: <aa071e4a-793d-4035-9d7e-04c07955b130@default>
> Date: Mon, 31 Mar 2014 08:30:53 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 17146@debbugs.gnu.org
>
> > This change is backward-incompatible, but is not in NEWS for some
> > reason. Needless to say, the canonical way of fixing the fallout is
> > not described in NEWS. Are functions that need Help mode supposed to
> > let-bind these hooks? If so, the patch below should fix the problem.
> > In any case, please document the change and the way to adapt to it in
> > NEWS.
>
> Please see bug #17109. FWIW, this regression really bothers me.
I read the mailing list, so I'm perfectly aware of that bug and the
related discussions. Please don't hijack this bug to hold it hostage
to that one. This bug is about a related issue, but one thing it is
_not_ about is reverting the change in question. So talking here
instead of on #17109 is not useful.
next prev parent reply other threads:[~2014-03-31 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 1:52 bug#17146: 24.4.50; File save with incapable coding system precluded by strange error message Nathan Trapuzzano
2014-03-31 15:16 ` Eli Zaretskii
2014-03-31 15:30 ` Drew Adams
2014-03-31 15:54 ` Eli Zaretskii [this message]
[not found] <<87ha6fyw1e.fsf@nbtrap.com>
[not found] ` <<83lhvqcsb3.fsf@gnu.org>
[not found] ` <<aa071e4a-793d-4035-9d7e-04c07955b130@default>
[not found] ` <<83ha6ecqj3.fsf@gnu.org>
2014-05-05 2:01 ` Drew Adams
2014-05-05 6:20 ` Eli Zaretskii
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=83ha6ecqj3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17146@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=nbtrap@nbtrap.com \
/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).