From: Gunnar Evermann <ge204@eng.cam.ac.uk>
Subject: enable-multibyte-characters is not defined in XEmacs
Date: 10 Dec 1999 13:59:26 +0000 [thread overview]
Message-ID: <mqqaenisxq9.fsf@eng.cam.ac.uk> (raw)
In XEmacs21.1.8-nomule using gnus-summary-refer-parent-article with
gnus-refer-article-method set to
(current (nnweb "refer" (nnweb-type dejanews)))
gives:
Signaling: (void-variable enable-multibyte-characters)
default-value(enable-multibyte-characters)
nnweb-init("refer")
nnweb-possibly-change-server("list.ding" "refer")
nnweb-request-article("<m366z8qjbq.fsf@quimbies.gnus.org>" "list.ding" "refer" nil)
gnus-request-article("<m366z8qjbq.fsf@quimbies.gnus.org>" "nnml:list.ding")
gnus-request-head("<m366z8qjbq.fsf@quimbies.gnus.org>" "nnml:list.ding")
gnus-read-header("<m366z8qjbq.fsf@quimbies.gnus.org>")
gnus-summary-insert-subject("<m366z8qjbq.fsf@quimbies.gnus.org>")
byte-code("..." [gnus-refer-article-methods nil gnus-override-method --dolist-temp--78826 gnus-check-server gnus-summary-insert-subject message-id number gnus-summary-select-article throw found t gnus-message 3 "Couldn't fetch article %s"] 6)
gnus-summary-refer-article("<m366z8qjbq.fsf@quimbies.gnus.org>")
gnus-summary-refer-parent-article(1)
call-interactively(gnus-summary-refer-parent-article)
--
Gunnar Evermann
Speech, Vision & Robotics Group
Cambridge University Engineering Department
next reply other threads:[~1999-12-10 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 13:59 Gunnar Evermann [this message]
1999-12-10 17:30 ` Shenghuo ZHU
1999-12-10 19:13 ` Gunnar Evermann
1999-12-10 20:19 ` Shenghuo ZHU
1999-12-10 20:51 ` Gunnar Evermann
1999-12-10 21:25 ` Shenghuo ZHU
1999-12-13 11:34 ` Gunnar Evermann
1999-12-14 6:16 ` Shenghuo ZHU
1999-12-14 11:52 ` Gunnar Evermann
1999-12-14 15:48 ` Shenghuo ZHU
1999-12-14 16:18 ` Gunnar Evermann
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=mqqaenisxq9.fsf@eng.cam.ac.uk \
--to=ge204@eng.cam.ac.uk \
/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).