From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: [Bug] Problems compiling spam.el and autoloading gnus-cite with recent CVS Gnus in (S)Xemacs
Date: Sun, 31 Dec 2006 12:44:04 +0100 [thread overview]
Message-ID: <v9vejswarf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <microsoft-free.877iw9znm2.fsf@youngs.au.com>
[ Resent ]
On Sat, Dec 30 2006, Steve Youngs wrote:
> * Nelson Ferreira <nelson.ferreira@ieee.org> writes:
>
> > While compiling a recent (Dec 29th CVS Gnus) with (S)XEmacs
Please include the detailed version numbers of (S)XEmacs when
reporting problems.
> > and the latest release packages I get the following error:
>
> > Compiling /home/njsf/sandboxes/gnus/lisp/spam.el...
> > While compiling toplevel forms in file
> > /home/njsf/sandboxes/gnus/lisp/spam.el:
> > !! Symbol's function definition is void ((ad-add-advice))
I wonder why `ad-add-advice' appears here. Maybe from
`dgnushack-make-auto-load'.
> I _can't_ reproduce this with...
>
> steve@sxemacs.org--2007/sxemacs--main--22.1.7--patch-7
>
> ...it builds fine for me.
I can't reproduce it neither with XEmacs 21.4 (patch 15) "Security
Through Obscurity" [Lucid] (x86_64-suse-linux, Mule\ ) of Fri Feb 11
2005 on helvede.
> > Is causing the following backtrace when viewing an article, on first
> > load of gnus-cite:
>
> > Debugger entered--Lisp error: (void-variable
> > gnus-message-citation-mode)
>
> Haven't tested this yet. Will report back later.
See the thread "Highlighting of different citation levels in
message-mode" and my answer to Norbert there:
<news:v9y7os14zi.fsf@marauder.physik.uni-ulm.de>
http://thread.gmane.org/v9y7os14zi.fsf%40marauder.physik.uni-ulm.de
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2006-12-31 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 5:30 Nelson Ferreira
2006-12-30 10:25 ` Steve Youngs
2006-12-30 11:44 ` Steve Youngs
2006-12-31 11:44 ` Reiner Steib [this message]
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=v9vejswarf.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).