Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el and missing functions
Date: Wed, 09 Oct 2002 10:53:49 -0400	[thread overview]
Message-ID: <m3it0b7jeq.fsf@heechee.beld.net> (raw)
In-Reply-To: <yotlwuosh1a5.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 09 Oct 2002 10:02:58 +0900")

On Wed, 09 Oct 2002, yamaoka@jpl.org wrote:
>> I fixed the BBDB errors with:
> 
>> ;; BBDB autoloads
>> (autoload 'bbdb-search "bbdb-com")
> 
> Unfortunately, it doesn't fix.  The byte-compiler still generates
> the byte-code which is equivalent to `(funcall 'bbdb-search args)'
> in the function `spam-check-bbdb'

> Since the macro definition of `bbdb-search' should be expanded
> before byte-compiling the function `spam-check-bbdb',
> bbdb-com.elc should be loaded at the compile time rather than
> autoloaded.  The following code will help only BBDB users who
> have already installed BBDB.

OK, I added your patch (if I understand correctly, it still autoloads
the bbdb-records function, but the bbdb-search macro needs special
treatment), but what do we do if the user does not have BBDB
installed?  

As far as I'm concerned, spam-check-bbdb can just be an empty function
without a BBDB installation, or it can raise an error.

Ted




  reply	other threads:[~2002-10-09 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 12:21 Katsumi Yamaoka
2002-10-08 14:42 ` Ted Zlatanov
2002-10-08 23:38   ` Jesper Harder
2002-10-08 23:57     ` François Pinard
2002-10-09  1:35       ` Jesper Harder
2002-10-09 14:54     ` Ted Zlatanov
2002-10-09  1:02   ` Katsumi Yamaoka
2002-10-09 14:53     ` Ted Zlatanov [this message]
2002-10-09 23:09       ` Alex Schroeder
2002-10-17  9:24   ` Katsumi Yamaoka
2002-10-18  1:31     ` Ted Zlatanov
2002-10-18  1:47       ` Katsumi Yamaoka

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=m3it0b7jeq.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    /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).