From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Problem saving attachment with latest CVS HEAD Gnus
Date: Tue, 21 Nov 2006 21:42:46 +0900 [thread overview]
Message-ID: <b4m3b8das3d.fsf@jpl.org> (raw)
In-Reply-To: <x71wnx6m5t.fsf@davestoy.homelinux.org>
>>>>> In <x71wnx6m5t.fsf@davestoy.homelinux.org> Dave Goldberg wrote:
> Just a data point: yesterday, after a bit of a hiatus I did a cvs
> update and got mm-decode.el 7.47 and just about all base64 encoded
> attachments became unsaveable. I run a MULE-enabled XEmacs 21.4.19 on
> cygwin. I'm not at work at the moment so can't provide the exact
> configuration. I guessed (apparently correctly) that the issue was
> with mm-decode.el and backed out to 7.46 and the problem has gone
> away.
How does the most recent trunk work? I've checked in in mm-util.el
in order to make `mm-string-to-multibyte' be an alias to `identity'
in (S)XEmacs. mm-decode.el 7.47 uses it while 7.46 used
`mm-string-as-multibyte', which breaks binary data in Emacs 23.
Though I'm not quite sure (because I cannot reproduce the problem
with (S)XEmacs), the most recent change in mm-util.el at least makes
XEmacs work fast and may possibly solve the problem.
Regards,
next prev parent reply other threads:[~2006-11-21 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 4:17 Nelson Ferreira
2006-11-21 7:50 ` Katsumi Yamaoka
2006-11-21 10:07 ` Katsumi Yamaoka
2006-11-21 12:04 ` Dave Goldberg
2006-11-21 12:42 ` Katsumi Yamaoka [this message]
2006-11-21 14:46 ` Dave Goldberg
2006-11-21 15:29 ` Katsumi Yamaoka
2006-11-22 4:48 ` Nelson Ferreira
2006-11-22 7:25 ` Katsumi Yamaoka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4m3b8das3d.fsf@jpl.org \
--to=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.
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 NNTP newsgroup(s).