From: amu@mit.edu (Aaron M. Ucko)
Cc: ding@gnus.org
Subject: Re: Why can't `gnus-draft-setup' be bytecompiled?
Date: 20 Mar 1998 21:09:14 -0500 [thread overview]
Message-ID: <udlogz0iylx.fsf@tux.mit.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 19 Mar 1998 07:51:09 -0500
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> amu@MIT.EDU (Aaron M. Ucko) writes:
>
> > That's a spurious argument. As of Gnus 5.5, 63 of the 79 elisp files
> > in Gnus required 'cl.
>
> They do? Where?
Right before they require Gnus, typically:
#amu(amu)@tux:/afs/sipb.mit.edu/contrib/emacs/packages/gnus-5.4.67/lisp
; fgrep -3 "(require 'cl)" *.el
cus-face.el-
cus-face.el-(require 'custom)
cus-face.el-
cus-face.el:(eval-and-compile (require 'cl))
cus-face.el-
cus-face.el-;;; Compatibility.
cus-face.el-
--
dgnushack.el-
dgnushack.el-(fset 'facep 'ignore)
dgnushack.el-
dgnushack.el:(require 'cl)
dgnushack.el-(require 'bytecomp)
dgnushack.el-(push "." load-path)
dgnushack.el-(require 'lpath)
--
earcon.el-(if (null (boundp 'running-xemacs))
earcon.el- (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version)))
earcon.el-
earcon.el:(eval-when-compile (require 'cl))
earcon.el-(require 'gnus)
earcon.el-(require 'gnus-audio)
earcon.el-(require 'gnus-art)
--
gnus-art.el-
gnus-art.el-;;; Code:
gnus-art.el-
gnus-art.el:(eval-when-compile (require 'cl))
gnus-art.el-
gnus-art.el-(require 'custom)
gnus-art.el-(require 'gnus)
--
etc., etc., etc.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
next prev parent reply other threads:[~1998-03-21 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-09 23:01 SL Baur
1998-03-09 23:19 ` Hrvoje Niksic
1998-03-13 21:39 ` Lars Magne Ingebrigtsen
1998-03-14 3:11 ` Hallvard B Furuseth
1998-03-14 3:23 ` Hrvoje Niksic
1998-03-14 4:09 ` Aaron M. Ucko
1998-03-19 12:30 ` Lars Magne Ingebrigtsen
1998-03-21 2:09 ` Aaron M. Ucko [this message]
1998-03-23 13:15 ` Lars Magne Ingebrigtsen
1998-03-14 2:29 ` Hallvard B Furuseth
1998-03-19 12:25 ` Lars Magne Ingebrigtsen
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=udlogz0iylx.fsf@tux.mit.edu \
--to=amu@mit.edu \
--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).