Gnus development mailing list
 help / color / mirror / Atom feed
* Re: "You should byte-compile Gnus" ?
       [not found]           ` <m2zltpe7e8.fsf@gmail.com>
@ 2008-02-25  9:43             ` Bastien
  0 siblings, 0 replies; only message in thread
From: Bastien @ 2008-02-25  9:43 UTC (permalink / raw)
  To: ding

William Xu <william.xwl@gmail.com> writes:

> "Charles philip Chan" <cpchan@sympatico.ca> 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: 
> "/Users/william/share/emacs/22.1.91/lisp/gnus/":
>
> ,----
> | zen:~/share/emacs/22.1.91/lisp/gnus$ ls -lthr gnus.el*
> | -rw-r--r--  1 william  staff    36K  2  4 18:42 gnus.el.gz
> | -rw-r--r--  1 william  staff   155K  2 21 20:02 gnus.elc
> | zen:~/share/emacs/22.1.91/lisp/gnus$ 
> `----
>
> The elc file is definitely newer than el file.
>
> Actually when i start emacs with `-Q', then start gnus, it won't
> complain that. 

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.  

-- 
Bastien



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-02-25  9:43 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <m2hcfxsnhf.fsf@gmail.com>
     [not found] ` <87mypph6oz.fsf@bzg.ath.cx>
     [not found]   ` <m2d4qlsesx.fsf@gmail.com>
     [not found]     ` <87hcfxh5uh.fsf@bzg.ath.cx>
     [not found]       ` <m2d4qlpjxn.fsf@gmail.com>
     [not found]         ` <87wsotv5m6.fsf@MagnumOpus.Mercurius>
     [not found]           ` <m2zltpe7e8.fsf@gmail.com>
2008-02-25  9:43             ` "You should byte-compile Gnus" ? Bastien

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).