Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: How to load spam.el just for gmane reporting?
Date: Thu, 02 Oct 2003 22:00:07 +0200	[thread overview]
Message-ID: <v91xtvquk8.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nr81v7aar.fsf@lockgroove.bwh.harvard.edu>

On Thu, Oct 02 2003, Ted Zlatanov wrote:

> On Thu, 25 Sep 2003, 4.uce.03.r.s@nurfuerspam.de wrote:
[...]
>> But I'm quite sure that this doesn't work, since
>> `spam-install-hooks-function' has no auto-load cookie.  I think we
>> should either add the cookie or clarify the instructions in the
>> manual.  Ted, WDYT?
>
> It should work :)  Can you suggest a fix?  

Already committed. ;-)

> I don't know about auto-load cookies.

When you add ";;;###autoload" before the defun, the function can be
called without requiring 'spam first.  The make process generates an
entry...

(autoload (quote spam-install-hooks-function) "spam" "\
Install the spam.el hooks" t nil)

... in `gnus-load.el'.  This file should be required when using a
stand-alone Gnus distribution, see (info "(gnus)Oort Gnus").  For the
version of Gnus bundled, the cookie is placed in `loaddefs.el' (and
this code is dumped into the Emacs binary, IIRC).

>> BTW: `spam-process-ham-in-spam-groups' and
>> `spam-process-ham-in-nonham-groups' aren't documented in the manual.
>
> I added those, take a look.

Thanks.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2003-10-02 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 19:12 Steinar Bang
2003-09-25 19:52 ` Reiner Steib
2003-09-27 22:45   ` Steinar Bang
2003-09-27 23:02     ` Steinar Bang
2003-09-28 13:46     ` Reiner Steib
2003-10-02 18:40   ` Ted Zlatanov
2003-10-02 20:00     ` Reiner Steib [this message]
2003-09-25 20:27 ` Ted Stern
2003-09-27 22:39   ` Steinar Bang
2003-09-27 23:08     ` Steinar Bang
2003-10-02 18:31     ` 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=v91xtvquk8.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --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).