From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam-get-article-as-filename needed?
Date: Mon, 24 Feb 2003 15:08:18 -0500 [thread overview]
Message-ID: <4nel5x4f2l.fsf@chubby.bwh.harvard.edu> (raw)
In-Reply-To: <ufzqda5sm.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 24 Feb 2003 12:32:09 -0600")
On Mon, 24 Feb 2003, kgreiner@xpediantsolutions.com wrote:
> 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.
I always compile from the command line ('make'). Is that wrong? It
seems to be the "right" way to compile, as it does several autoloading
tricks.
Ted
prev parent reply other threads:[~2003-02-24 20:08 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
2003-02-24 20:08 ` Ted Zlatanov [this message]
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=4nel5x4f2l.fsf@chubby.bwh.harvard.edu \
--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).