From: Andi Hechtbauer <anti@spin.de>
Cc: ding@gnus.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: Wrong type argument: stringp when Generating cus-load.el
Date: Thu, 07 Nov 2002 19:48:12 +0100 [thread overview]
Message-ID: <878z059pxv.fsf@pod.hq.spin.de> (raw)
In-Reply-To: <yotlfzudcuac.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 07 Nov 2002 23:46:03 +0900")
Hi,
[CVS gnus wouldn't compile with cus-dep.el(c) in emacs21(-el) 21.2-5]
Andi> I just installed the .el files. Hopefully this is a more
Andi> interessting Backtrace now: [...]
Katsumi> I see. That file is the thing of Emacs 21.3.50, and,
Katsumi> moreover, there is a bug.
Hm, if that is true, debian is to blame. Or me, living on the
unstable edge ;-)
Rob Browning <rlb@defaultvalue.org> (Cc set) packaged this file with
emacs21-el Version 21.2-5 -- the file itself has no hint about
version. And changelog.Debian.gz isn't suggesting this, either.
M-x version tells me I'd be running 21.2.2.
Checking with a freshly downloaded 21.2 tarball shows this:
.../emacs-21.2/lisp$ diff cus-dep.el ~/tmp/cus-dep.el-debian
38c38
< (all-subdirs command-line-args-left)
---
> (all-subdirs (sort command-line-args-left 'string<))
88a89,90
> ;; So x and no-x builds won't differ.
> (setq members (sort members 'string<))
so obviously the debian maintainer applied a patch.
Andi> Debugger entered--Lisp error: (wrong-type-argument stringp
Andi> (mm-inline-text-html-with-w3m-keymap custom-variable))
Andi> (setq members (sort members (quote string<)))
Katsumi> It has been fixed by RMS as follows:
,----
| 2002-09-19 Richard M. Stallman <rms@gnu.org>
|
| * cus-dep.el (custom-make-dependencies): Fix previous change.
|
| 2002-09-18 Richard M. Stallman <rms@gnu.org>
| [...]
| * cus-dep.el (custom-make-dependencies): Sort MEMBERS before use.
`----
After replacing the debian cus-dep.el with the tarball one, and byte
compiling cus-dep.el, cvs gnus compiles as expected.
Thank you so much for looking into this!
Andi
next prev parent reply other threads:[~2002-11-07 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 2:13 Andi Hechtbauer
2002-11-07 4:18 ` Katsumi Yamaoka
2002-11-07 8:14 ` Manoj Srivastava
2002-11-07 9:07 ` Katsumi Yamaoka
2002-11-07 11:59 ` Andi Hechtbauer
2002-11-07 12:14 ` Katsumi Yamaoka
2002-11-07 12:52 ` Andi Hechtbauer
2002-11-07 14:46 ` Katsumi Yamaoka
2002-11-07 18:48 ` Andi Hechtbauer [this message]
2002-11-07 19:04 ` Rob Browning
2002-11-07 22:13 ` Katsumi Yamaoka
2002-11-07 22:24 ` Katsumi Yamaoka
2002-11-08 2:02 ` Manoj Srivastava
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=878z059pxv.fsf@pod.hq.spin.de \
--to=anti@spin.de \
--cc=ding@gnus.org \
--cc=rlb@defaultvalue.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).