From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: MIME decoding broken on Win NT
Date: 24 Nov 1998 21:19:32 +0100 [thread overview]
Message-ID: <m34sroc08b.fsf@sparky.gnus.org> (raw)
In-Reply-To: Shenghuo ZHU's message of "24 Nov 1998 14:31:03 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> 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?
The important thing about the macro is that it executes in a unibyte
buffer; the actual coding system is less important. (If it isn't a
unibyte buffer, the Emacs base64 code does not do what one would think
it does.) So I think the name is ok as it is now.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-11-24 20:19 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
1998-11-24 20:19 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m34sroc08b.fsf@sparky.gnus.org \
--to=larsi@gnus.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).