From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: nndraft:queue in 5.8.5?
Date: 20 Aug 2000 10:33:37 +0200 [thread overview]
Message-ID: <878ztsfi1q.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m3r97xhrp6.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Gnus has a pretty deep Lisp eval depth (lots of macros that create
> lexical environments (ahem)), and when running Gnus uncompiled,
Perhaps it's time to apply the following patch? Unfortunately, Emacs
and XEmacs both have deprecated one of "byte-code-function-p" and
"compiled-function-p", but not the same. :-/ The following code will
therefore result in a compilation-time warning on XEmacs 21.1, but on
XEmacs 21.2, "byte-code-function-p" is an FSF compatibility alias, and
there won't be any warning.
Index: gnus.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus.el,v
retrieving revision 5.141
diff -u -r5.141 gnus.el
--- gnus.el 2000/07/13 23:11:45 5.141
+++ gnus.el 2000/08/12 17:27:10
@@ -2896,6 +2896,9 @@
startup level. If ARG is non-nil and not a positive number, Gnus will
prompt the user for the name of an NNTP server to use."
(interactive "P")
+ (unless (byte-code-function-p (symbol-function 'gnus))
+ (message "You really should byte-compile Gnus.")
+ (sit-for 2))
(gnus-1 arg dont-connect slave))
;; Allow redefinition of Gnus functions.
next prev parent reply other threads:[~2000-08-20 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-22 9:33 Pavel Janik ml.
2000-04-22 13:16 ` Lars Magne Ingebrigtsen
2000-04-23 20:03 ` Pavel Janik ml.
2000-04-24 14:33 ` Lars Magne Ingebrigtsen
2000-04-24 17:28 ` Pavel Janik ml.
2000-08-10 18:55 ` Lars Magne Ingebrigtsen
2000-08-20 8:33 ` Florian Weimer [this message]
2001-12-31 8:20 ` Lars Magne Ingebrigtsen
2000-04-24 15:57 ` Pavel Janik ml.
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=878ztsfi1q.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).