From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: MIME decoding broken on Win NT
Date: 24 Nov 1998 14:31:03 -0500 [thread overview]
Message-ID: <5bd86cga6g.fsf@schnapps.cs.rochester.edu> (raw)
In-Reply-To: <uemqsrjix.fsf@ultraman.geoworks.com>
>>>>> "Matt" == Matt Armstrong <matta@geoworks.com> writes:
Matt> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>> + * mm-util.el (mm-with-unibyte-buffer): Use binary instead of nil.
Matt> This has fixed the problem. Exported binary files are no longer
Matt> corrupt under WinNT. Thanks!
This make situation more complicated. Kai Grossjohann reported that it
did not work in Gnu Emacs, at least some ugly message displayed. What
happens in XEmacs?
>> mm-with-binary-buffer seems to be a better name than
>> mm-with-unibyte-buffer.
Matt> I thought the same. In fact, I didn't make the change you made
Matt> above because I thought "unibyte" meant something special and
Matt> not just binary.
Lars, any comments?
--
Shenghuo
next prev parent reply other threads:[~1998-11-24 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 20:51 Matt Armstrong
1998-11-23 21:03 ` Shenghuo ZHU
1998-11-24 10:15 ` Lars Magne Ingebrigtsen
1998-11-24 8:50 ` Shenghuo ZHU
1998-11-24 19:13 ` Matt Armstrong
1998-11-24 19:31 ` Shenghuo ZHU [this message]
1998-11-24 20:19 ` Lars Magne Ingebrigtsen
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=5bd86cga6g.fsf@schnapps.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).