From: Jason R Mastaler <jason@mastaler.com>
Subject: XEmacs 21.1.9 breaks Gnus v5.8 (get-charset-property)
Date: 14 Feb 2000 14:00:02 -0700 [thread overview]
Message-ID: <m3g0uv4i0d.fsf@bodhi.in.mastaler.com> (raw)
When trying to send mail from XEmacs 21.1.9 and Gnus v5.8.x (latest
CVS), I get the following error and backtrace:
Signaling: (void-function get-charset-property)
get-charset-property(ascii prefered-coding-system)
mm-preferred-coding-system(ascii)
mm-mime-charset(ascii)
mapcar(mm-mime-charset (ascii))
rfc2047-encodable-p()
mail-encode-encoded-word-buffer()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
It looks like Andreas Jaeger reported this problem to xemacs-beta back
in early December, but nothing was done about it. See:
<URL:http://www.xemacs.org/list-archives/xemacs-beta/199912/msg00123.html>
next reply other threads:[~2000-02-14 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 21:00 Jason R Mastaler [this message]
2000-02-15 7:28 ` Florian Weimer
2000-02-17 8:31 ` Jason R Mastaler
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=m3g0uv4i0d.fsf@bodhi.in.mastaler.com \
--to=jason@mastaler.com \
/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).