Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <steve@sxemacs.org>
Subject: Re: [Bug] Problems compiling spam.el and autoloading gnus-cite with recent CVS Gnus in (S)Xemacs
Date: Sat, 30 Dec 2006 20:25:57 +1000	[thread overview]
Message-ID: <microsoft-free.877iw9znm2.fsf@youngs.au.com> (raw)
In-Reply-To: <m33b6yhrww.fsf.nfl.656d6163732e676e75732e67656e6572616c.00@tuxie.homelinux.net> (Nelson Ferreira's message of "Sat\, 30 Dec 2006 00\:30\:23 -0500")

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

* Nelson Ferreira <nelson.ferreira@ieee.org> writes:

  > Hi all,
  > While compiling a recent (Dec 29th CVS Gnus) with (S)XEmacs 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 _can't_ reproduce this with...

  steve@sxemacs.org--2007/sxemacs--main--22.1.7--patch-7

...it builds fine for me.

  > In addition, the recent change in gnus-cite:

[...]

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


-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve@sxemacs.org>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 312 bytes --]

  reply	other threads:[~2006-12-30 10:25 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 [this message]
2006-12-30 11:44   ` Steve Youngs
2006-12-31 11:44   ` Reiner Steib

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=microsoft-free.877iw9znm2.fsf@youngs.au.com \
    --to=steve@sxemacs.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).