From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: pgnus 0.94 Signaling: (void-variable buffer-file-coding-system)
Date: 11 Jul 1999 11:03:01 +0200 [thread overview]
Message-ID: <m3btdjwoca.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Shenghuo ZHU's message of "11 Jul 1999 00:20:37 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> | (let ((coding-system-for-write
> | (if (equal "text" (mm-handle-media-supertype handle))
> | buffer-file-coding-system
> | 'binary))
> `--------
>
> I guess using nil instead of buffer-file-coding-system should fix the
> bug, because in XEmacs w/ mule, buffer-file-coding-system is used for
> writing if coding-system-for-write is nil, and in XEmacs w/o mule, it
> will not cause unbounded error.
Perhaps coding-system-for-write should be 'binary in all cases, since
we are in `mm-with-unibyte-buffer' anyway... I've made this fix to
0.96.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-07-11 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 20:49 Roman Milner
1999-07-11 4:20 ` Shenghuo ZHU
1999-07-11 9:03 ` 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=m3btdjwoca.fsf@quimbies.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).