From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: gnus-agentize versus emacs 20 mapc
Date: Tue, 25 Nov 2003 08:57:42 +0900 [thread overview]
Message-ID: <b9y4qwtmia1.fsf@jpl.org> (raw)
In-Reply-To: <87oev1uyzw.fsf@zip.com.au>
>>>>> In <87oev1uyzw.fsf@zip.com.au>
>>>>> Kevin Ryde <user42@zip.com.au> wrote:
> I tried to startup today's cvs under emacs 20 but it died in
> gnus-agentize, apparently missing mapc
> Signaling: (void-function mapc)
[...]
> Does one have to require 'cl to use mapc, not just eval-when-compile?
> I'm not up with the way that stuff is supposed to work.
> If gnus-agentize is only iterating over a few methods then perhaps
> just mapcar would be enough.
I have the same opinion with you. Developers, if you think Gnus
still supports Emacs 20, please do so. Or should I add the
compiler macro to dgnushack.el for `mapc'?
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2003-11-24 23:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 23:29 Kevin Ryde
2003-11-24 23:57 ` Katsumi Yamaoka [this message]
2003-11-25 3:45 ` Kevin Greiner
2003-11-25 4:18 ` Katsumi Yamaoka
2003-11-25 21:47 ` Kevin Ryde
2003-11-26 2:13 ` Katsumi Yamaoka
2003-11-26 11:34 ` Using CL in Gnus (was: gnus-agentize versus emacs 20 mapc) Reiner Steib
2003-11-26 12:23 ` Using CL in Gnus Katsumi Yamaoka
2003-11-26 17:38 ` Reiner Steib
2003-11-26 19:46 ` Karl Pflästerer
2003-11-27 22:41 ` Reiner Steib
2003-11-28 16:30 ` Karl Pflästerer
2003-11-28 17:08 ` Jesper Harder
2003-11-29 8:04 ` Miles Bader
2003-11-29 9:10 ` Jesper Harder
2003-11-29 12:37 ` Miles Bader
2003-12-01 21:23 ` Ted Zlatanov
2003-12-01 22:54 ` Katsumi Yamaoka
2003-11-30 13:22 ` Using CL in Gnus (was: gnus-agentize versus emacs 20 mapc) Per Abrahamsen
2003-11-28 21:31 ` gnus-agentize versus emacs 20 mapc Kevin Ryde
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=b9y4qwtmia1.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).