From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Thu, 11 Nov 2004 11:45:44 -0600 (CST) [thread overview]
Message-ID: <200411111745.iABHji207636@raven.dms.auburn.edu> (raw)
In-Reply-To: <b9y8y98prb8.fsf@jpl.org> (message from Katsumi Yamaoka on Thu, 11 Nov 2004 20:18:19 +0900)
Katsumi Yamaoka wrote:
Although I'm not sure of it, the following patch seems to solve
the problem.
Your patch does not seem to solve a related problem I reported earlier
on emacs-devel, so it probably is not a complete solution:
Changes in byte compilation which must be less than a day old, have
strange effects. `winner' is no longer usable when winner.elc is
used, but still seems to work fine when winner.el is used.
After `emacs -q' I get the following ielm run:
*** Welcome to IELM *** Type (describe-mode) for help.
ELISP> (load "winner")
t
ELISP> (winner-sorted-window-list)
*** Eval error *** Symbol's function definition is void: t
ELISP> (load "winner.el")
t
ELISP> (winner-sorted-window-list)
(#<window 3 on *ielm*>)
ELISP>
Byte compiling winner.el produces:
Compiling file /home/teirllm/emacscvsdir/emacs/lisp/winner.el at Tue
Nov 9 08:32:15 2004
Entering directory `/home/teirllm/emacscvsdir/emacs/lisp/'
winner.el:52:14:Warning: Function `gensym' from cl package called at
runtime
winner.el:56:10:Warning: Function `gensym' from cl package called at
runtime
In winner-sorted-window-list:
winner.el:125:10:Warning: attempt to inline `t' before it was defined
winner.el:124:4:Warning: `t' called as a function
In winner-make-point-alist:
winner.el:284:33:Warning: attempt to inline `t' before it was defined
winner.el:285:44:Warning: `t' called as a function
In end of data:
winner.el:488:1:Warning: the function `t' is not known to be defined.
Comments:
The first two warnings are probably legitimate.
The function `t' stuff appears to be a bug in byte compilation.
next prev parent reply other threads:[~2004-11-11 17:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877jouepy8.fsf@telia.com>
[not found] ` <b9yd5ymkq11.fsf@jpl.org>
2004-11-11 7:40 ` Katsumi Yamaoka
2004-11-11 11:18 ` Katsumi Yamaoka
2004-11-11 17:45 ` Luc Teirlinck [this message]
2004-11-11 21:55 ` Stefan
2004-11-11 22:41 ` Luc Teirlinck
2004-11-11 22:54 ` Luc Teirlinck
2004-11-12 0:22 ` Katsumi Yamaoka
2004-11-12 3:57 ` Stefan Monnier
2004-11-12 4:30 ` Katsumi Yamaoka
2004-11-13 23:03 ` Stefan
2004-11-14 0:14 ` Katsumi Yamaoka
2004-11-14 5:21 ` Stefan
2004-11-14 6:10 ` Katsumi Yamaoka
2004-11-14 6:36 ` Stefan
2004-11-14 13:44 ` Katsumi Yamaoka
2004-11-14 17:29 ` Luc Teirlinck
2004-11-14 19:17 ` Stefan Monnier
2004-11-15 14:00 ` Richard Stallman
2004-11-15 15:36 ` Stefan Monnier
2004-11-15 23:22 ` Miles Bader
2004-11-15 23:28 ` Stefan Monnier
2004-11-15 23:38 ` Miles Bader
2004-11-15 23:44 ` Stefan Monnier
2004-11-15 23:57 ` Luc Teirlinck
2004-11-16 1:29 ` Nick Roberts
2004-11-16 1:49 ` Luc Teirlinck
2004-11-16 2:19 ` Luc Teirlinck
2004-11-16 16:49 ` Richard Stallman
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=200411111745.iABHji207636@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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).