From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: spam-get-article-as-filename needed?
Date: Mon, 24 Feb 2003 12:32:09 -0600 [thread overview]
Message-ID: <ufzqda5sm.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <4n4r6t5ytt.fsf@chubby.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Mon, 24 Feb 2003, kgreiner@xpediantsolutions.com wrote:
>> I was looking at the compilation logs only to see that spam.el
>> generated a couple of warning messages concerning
>> nnml-current-directory and nnml-possibly-change-directory.
>
> Strange, I was not seeing those warnings.
If you compile in the same emacs as you are running gnus, you won't
see these as gnus will have already loaded nnml. I only see this sort
of message when I compile in a new emacs that has never run gnus.
>> After checking a little further, I found that
>> 1) The only dependencies to nnml are in
>> spam-get-article-as-filename.
>> 2) spam-get-article-as-filename is functionally equivalent to
>> nnml-article-to-file except that the later appears to handle
>> compressed files (see nnml-use-compressed-files).
>> 3) I can't find any calls to spam-get-article-as-filename.
>>
>> I don't want to touch spam.el since I'm not at all familiar with
>> that code. Still, I'd like to see the compilation warnings
>> resolved.
>>
>> It seems to me that the options are:
>> 1) Add (require 'nnml) to spam.el
>> 2) Delete spam-get-article-as-filename
>> 3) Rewrite spam-get-article-as-filename to implicitly depend on
>> nnml-article-as-file. For example,
>> (defun spam-get-article-as-filename (article)
>> (funcall 'nnml-article-to-file article))
>
> The original intent was (and still is) to allow training a spam/ham
> backend directly from the files, rather than through the less
> efficient parameter passing. It's not useful yet, however, so I
> commented the code out for the time being. It will come back when I
> put a bunch of other things in place, and I'll keep in mind your issue
> with nnml symbols.
>
Thanks. That's what I hoped to hear.
Kevin
next prev parent reply other threads:[~2003-02-24 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 17:57 Kevin Greiner
2003-02-24 18:16 ` Ted Zlatanov
2003-02-24 18:32 ` Kevin Greiner [this message]
2003-02-24 20:08 ` 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=ufzqda5sm.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).