From: Matt Pharr <mmp@graphics.stanford.edu>
Cc: bugs@gnus.org
Subject: Bug: void-function string-to-char-list
Date: 17 Dec 1999 16:23:19 -0800 [thread overview]
Message-ID: <kh0wvqdf66g.fsf@abuffer.Stanford.EDU> (raw)
I'm getting the following bug out with a 5.8.3 that's about 4 hours old
from the CVS archive when I attach a C file and try to send it.
-matt
Signaling: (void-function string-to-char-list)
string-to-char-list("][()<>@,;:\\\"/?=")
rfc2047-dissect-region(1 8)
rfc2047-encode-region(1 8)
mail-encode-encoded-word-string("tetra.c")
mml-insert-mime-headers((part (type . "application/octet-stream") (filename . "~/project/peercy/tetra.c") (disposition . "attachment") (description . "tetra.c") (contents . "")) "application/octet-stream" nil 7bit)
mml-generate-mime-1((part (type . "application/octet-stream") (filename . "~/project/peercy/tetra.c") (disposition . "attachment") (description . "tetra.c") (contents . "")))
mml-generate-mime-1((multipart (type . "mixed") (part (type . "text/plain") (contents . "\nSome bugs with the triangle output--missing space between each set of six\nnumbers, easily enough fixed.\n\nMore importantly (and not yet fixed), the point also needs to be\ntransformed by the current matrix before being printed--I've done what I\nthink are the obvious fixes for this, but now I'm getting pretty goofy\nresults. Attached is the current state of the code. Any thoughts?\n\n-matt\n\n")) (part (type . "application/octet-stream") (filename . "~/project/peercy/tetra.c") (disposition . "attachment") (description . "tetra.c") (contents . "")) (part (type . "text/plain") (contents . "\n\n\n"))))
mml-generate-mime()
message-encode-message-body()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
next reply other threads:[~1999-12-18 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-18 0:23 Matt Pharr [this message]
1999-12-18 0:40 ` Shenghuo ZHU
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=kh0wvqdf66g.fsf@abuffer.Stanford.EDU \
--to=mmp@graphics.stanford.edu \
--cc=bugs@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).