From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Using CL in Gnus (was: gnus-agentize versus emacs 20 mapc)
Date: Sun, 30 Nov 2003 14:22:42 +0100 [thread overview]
Message-ID: <rjoeuung7x.fsf@sheridan.dina.kvl.dk> (raw)
In-Reply-To: <v9y8u3cqiq.fsf@marauder.physik.uni-ulm.de>
The only Emacs where we need to worry about not including the cl
runtime is "the next version of GNU Emacs".
RMS do not want the cl namespace to clutter the pristine GNU Emacs,
which mean that Gnus that the bundled version of Gnus should not load
the cl runtime. Since this list concern the development version of
Gnus, which will be available unbundled for older Emacsen and bundled
only in a future Emacs release, the "future Emacs release" is the only
version where we need to avoid cl.
In other words, using functions like mapc that requires the cl runtime
in older Emacsen (or XEmacs) are fine, as long as they don't require
cl in the CVS version of Emacs.
next prev parent reply other threads:[~2003-11-30 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 23:29 gnus-agentize versus emacs 20 mapc Kevin Ryde
2003-11-24 23:57 ` Katsumi Yamaoka
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 ` Per Abrahamsen [this message]
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=rjoeuung7x.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).