From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: pgnus 0.94 Signaling: (void-variable buffer-file-coding-system)
Date: 11 Jul 1999 00:20:37 -0400 [thread overview]
Message-ID: <2npv1zvmui.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Roman Milner's message of "09 Jul 1999 15:49:15 -0500"
>>>>> "Roman" == Roman Milner <roman@speeder.com> writes:
Roman> On XEmacs 21.3 sans mule - when I try to save a text/html mime part:
Roman> Signaling: (void-variable buffer-file-coding-system)
Roman> mm-save-part-to-file((#<buffer " *mm*<2>"> ("text/html" (name
Roman> . "footer.html")) nil (lambda nil (let ... ... ...)) ("inline"
Roman> (filename . "footer.html")) "footer.html" nil nil) "~/footer.html")
Roman> mm-save-part((#<buffer " *mm*<2>"> ("text/html" (name
Roman> . "footer.html")) nil (lambda nil (let ... ... ...)) ("inline"
Roman> (filename . "footer.html")) "footer.html" nil nil))
Roman> #<compiled-function nil "...(13)" [gnus-article-check-buffer
Roman> get-text-property gnus-data data mm-save-part] 3
Roman> ("/usr/src/elisp/sgnus/gnus-art.elc" . 74855) nil>()
Roman> call-interactively(gnus-mime-save-part)
Roman> gnus-mime-button-menu(#<buttondown-event button3>)
Roman> call-interactively(gnus-mime-button-menu)
,-------- Line 569 of mm-decode.el
| (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.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-07-11 4:20 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 [this message]
1999-07-11 9:03 ` 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=2npv1zvmui.fsf@tiger.jia.vnet \
--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).