From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25658@debbugs.gnu.org
Subject: bug#25658: 26.0.50; ELisp part in a mail isn't encoded properly
Date: Mon, 13 Feb 2017 17:31:03 +0900 [thread overview]
Message-ID: <b4mh93y1ohk.fsf@jpl.org> (raw)
In-Reply-To: <b4m7f50ks55.fsf@jpl.org>
On Mon, 13 Feb 2017 07:44:07 +0200, Eli Zaretskii wrote:
>> cd lisp/gnus
>> egrep '\((decode|encode)-coding-region' *.el|wc -l
>> => 10
>> are they all potentially bugs?
> Not necessarily, they need to be reviewed one by one.
Ok. But I personally got to think *-coding-region should never
be used anymore.
> My question was triggered by the fact that "what Gnus wants" was so
> much simpler and obviously correct that it was a clear winner IMO. If
> the other places are all of the same variety, then yes, I'd suggest to
> make similar replacements there as well.
I see, however it's not so easy to simplify the codes so as to
achieve just "what Gnus wants" perfectly (I mean using *-coding-
string for all the cases).
Instead, I've modified `mm-encode-body' for the emergency fix.
In the Emacs master, only `mml-generate-mime-1' uses it.
(`rfc2231-encode-string' uses it as well but now we use
`rfc2047-encode-parameter' instead for encoding a file name.)
Regards,
prev parent reply other threads:[~2017-02-13 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 2:35 bug#25658: 26.0.50; ELisp part in a mail isn't encoded properly Katsumi Yamaoka
2017-02-10 0:56 ` Katsumi Yamaoka
2017-02-10 7:51 ` Eli Zaretskii
2017-02-10 17:33 ` Glenn Morris
2017-02-12 23:05 ` Katsumi Yamaoka
2017-02-13 2:03 ` Glenn Morris
2017-02-13 5:44 ` Eli Zaretskii
2017-02-13 8:31 ` Katsumi Yamaoka [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://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=b4mh93y1ohk.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=25658@debbugs.gnu.org \
--cc=eliz@gnu.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).