On 2009-01-02 01:47 +, Joe Fineman wrote:
However, there is an oddity. Whenever I start Gnus, I get a message
You should byte-compile Gnus. It is already byte-compiled AFAICT --
every .el file in lisp/gnus has its .elc file. Why am I being told
this?
This is to tell users to compile
by installing
Gnus 5.10.10.
However, there is an oddity. Whenever I start Gnus, I get a message
You should byte-compile Gnus. It is already byte-compiled AFAICT --
every .el file in lisp/gnus has its .elc file. Why am I being told
this?
Because the function `gnus' isn't byte-compiled. Check `M
Reiner Steib reinersteib+gm...@imap.cc writes:
Because the function `gnus' isn't byte-compiled. Check `M-x
locate-library RET gnus RET' if it picks up the .el or .elc file.
I did look at it, before I posted. The file is byte-compiled, as is
the function gnus.
--
--- Joe Fineman
I have just installed Gnus 5.10.10 under Emacs 22.3.1. It has gotten
rid of a number of annoyances, including especially the problem in
reading certain groups at Mozzarella, which I described some time ago.
However, there is an oddity. Whenever I start Gnus, I get a message
You should byte
Reiner Steib writes:
On Thu, Mar 06 2008, Hallvard B Furuseth wrote:
(...)
So the test needs to see past the defadvise.
I think advising `gnus' is rare enough that adding a hint like ...
2. Add the `compile' flag to the arglist of defadvice. E.g.;
(defadvice FUNCTION (CLASS NAME ...
-is-compiled) ;declare constant before use
(defun gnus (...)
...
(unless gnus-is-compiled
(message You should byte-compile Gnus)
...))
(defconst gnus-is-compiled (byte-code-function-p (symbol-function 'gnus)))
--
Hallvard
___
info
On Thu, Mar 06 2008, Hallvard B Furuseth wrote:
Katsumi Yamaoka writes:
[...]
I think the reason you should compile Gnus is that it can be
horribly slow uncompiled. But that is the gnus _package_, not the
gnus _function_.
Yes.
So the test needs to see past the defadvise.
I think
Charles philip Chan [EMAIL PROTECTED] writes:
No, it is not complaining about you gnus config file. Either your el
files are newer then your elc files or you have another copy of gnus.el
somewhere that is being picked up.
I use `describe-function gnus' for locating gnus.el, it is under:
William Xu [EMAIL PROTECTED] writes:
Charles philip Chan [EMAIL PROTECTED] writes:
No, it is not complaining about you gnus config file. Either your el
files are newer then your elc files or you have another copy of gnus.el
somewhere that is being picked up.
I use `describe-function gnus'
Bastien [EMAIL PROTECTED] writes:
Maybe you should compare the location of C-h f gnus RET when running
emacs -Q against its location when you're running a normal emacs
session, with all your config.
Okay, I caught it. It is all because I have defadvice gnus in my config file:
,
|
William Xu wrote:
I don't quite understand, though. A defadvice will forbid it from being
byte-compiled?
The default value of `ad-default-compilation-action' is `maybe'
which means not to compile advised functions if bytecomp.elc is
not loaded. Though that advice to gnus seems needless now
Katsumi Yamaoka wrote:
Though that advice to gnus seems needless now ;-),
Sorry, I meant `gnus-other-frame'. (It is useful for finding out
the Gnus frame that is behind the other frames.)
___
info-gnus-english mailing list
info-gnus-english@gnu.org
Katsumi Yamaoka [EMAIL PROTECTED] writes:
The default value of `ad-default-compilation-action' is `maybe'
which means not to compile advised functions if bytecomp.elc is
not loaded. Though that advice to gnus seems needless now ;-),
there are several ways to force the byte-compilation:
1.
Whenever i start gnus, it welcomes me with You should byte-compile
Gnus. I looked into /Users/william/share/emacs/22.1.91/lisp/gnus
(emacs-version is 22.1.91.2):
,
| zen:~/share/emacs/22.1.91/lisp/gnus$ ls *.elc | wc -l
| 135
| zen:~/share/emacs/22.1.91/lisp/gnus$ ls *.el.gz | wc -l
William Xu [EMAIL PROTECTED] writes:
Whenever i start gnus, it welcomes me with You should byte-compile
Gnus. I looked into /Users/william/share/emacs/22.1.91/lisp/gnus
(emacs-version is 22.1.91.2):
,
| zen:~/share/emacs/22.1.91/lisp/gnus$ ls *.elc | wc -l
| 135
| zen:~/share
Bastien [EMAIL PROTECTED] writes:
You sure your .el files are not more recent than your .elc files?
Yes(or No? naughty English...). All .elc files are more recent.
--
William
http://williamxu.net9.org
___
info-gnus-english mailing list
-p (symbol-function 'gnus))
| (message You should byte-compile Gnus)
| (sit-for 2))
| (gnus-1 arg dont-connect slave))
`
So it looks like either your gnus.el is not byte-compiled or there is
another one lingering somewhere on your system.
--
Bastien
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 should byte-compile Gnus)
| (sit-for 2))
| (gnus-1 arg dont-connect slave))
`
So it looks like either
William Xu [EMAIL PROTECTED] writes:
Ooh, it is complaining about the .gnus? My gnus config file is in
xwl-gnus.el. All my configs are not byte-compiled, and i don't like
to, since at times it confuses me whenever i forgot to recompile after
modifications.
No, it is not complaining about you
Hi,
I checked out No Gnus from CVS into my $HOME, made ./configure make,
added it to emacs (as the first things to do)
(add-to-list 'load-path ~/repos/gnus/lisp)
(require 'gnus-load)
but still it's saying You should byte-compile gnus on startup. But it
is byte-compiled. For any *.el file
20 matches
Mail list logo
