From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: void function coding-system-get
Date: Sat, 12 Feb 2005 09:08:51 +0900 [thread overview]
Message-ID: <yotlis4ytzak.fsf@jpl.org> (raw)
In-Reply-To: <mj7hdkic456.fsf@mm117419-pc.MITRE.ORG>
>>>>> In <mj7hdkic456.fsf@mm117419-pc.MITRE.ORG>
>>>>> david.goldberg6@verizon.net (David S. Goldberg) wrote:
> Updated Gnus from CVS this morning, but it's been quite some time
> since I've sent a jpeg attachment. Sending a PDF didn't have this
> problem. Here's the backtrace I get after hitting \C-c\C-c in the
> message buffer.
> Debugger entered--Lisp error: (void-function coding-system-get)
> coding-system-get(binary :mime-charset)
> mm-coding-system-to-mime-charset(binary)
I'm sorry to have forgotten non-Mule XEmacs. Fixed.
next prev parent reply other threads:[~2005-02-12 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 19:01 David S. Goldberg
2005-02-11 19:36 ` David S. Goldberg
2005-02-12 0:08 ` Katsumi Yamaoka [this message]
2005-02-15 2:45 ` Dave Goldberg
2005-02-15 16:01 ` David S. Goldberg
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=yotlis4ytzak.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@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).