From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Warnings when byte-compiling spam.el
Date: Tue, 07 Jan 2003 05:51:19 +0100 [thread overview]
Message-ID: <m3ptr9imuw.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <4n8yxy881k.fsf@lockgroove.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
>> While compiling the end of the data in file
>> /csa/forum/emerick/gnus/lisp/spam.el: ** The following functions
>> are not known to be defined: spam-BBDB-register-routine,
>> bbdb-create-internal, spam-enter-ham-BBDB
>
> I think this is because of the mess with the BBDB macros defined in
> bbdb-com.el. It shouldn't be a problem because of the condition-case,
> I thought. Can anyone suggest a better way to deal with those macros,
> or point me to the Emacs Lisp features I'm not aware of to hush up the
> warnings?
Just put the functions/macros in the maybe-bind lists in lpath.el to
make the warning messages go away.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-01-07 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 14:48 Emerick Rogul
2003-01-06 18:09 ` Ted Zlatanov
2003-01-07 4:51 ` Lars Magne Ingebrigtsen [this message]
2003-01-07 13:15 ` Ted Zlatanov
2003-01-08 3:57 ` Lars Magne Ingebrigtsen
2003-01-08 20:14 ` Ted Zlatanov
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=m3ptr9imuw.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).