Gnus development mailing list
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: irritated by all those "no new mail" messages
Date: 02 Nov 1999 10:36:43 -0800	[thread overview]
Message-ID: <m1zowwagg4.fsf@halfdome.holdit.com> (raw)
In-Reply-To: Stephen Zander's message of "02 Nov 1999 08:33:51 -0800"

>>>>> "Stephen" == Stephen Zander <gibreel@pobox.com> writes:

Stephen> FWIW, I have the following:

Stephen>   (setq nnmail-spool-file '((directory :path 
Stephen>        (concat gnus-directory ".incoming/"))

Stephen> and pgnus just works, ie I get one 'Check new mail' message no mater
Stephen> how many spools do or do not have anything in them.

(describe-variable 'nnmail-spool-file) ==>

    nnmail-spool-file's value is 
    ((file))


    Documentation:
    *Where the mail backends will look for incoming mail.
    This variable is a list of mail source specifiers.
    This variable is obsolete; `mail-sources' should be used instead.

    You can customize this variable.

I see "obsolete" and I take it to heart.  I'm using mail-sources
instead, as instructed.  I have mine set to this:

    ((directory :path "~/.incoming/" :predicate
                (lambda
                  (f)
                  (not
                   (zerop
                    (nth 7
                         (file-attributes f)))))))

Why am I getting a message for every single nnml group?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!


  reply	other threads:[~1999-11-02 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-02 15:39 Randal L. Schwartz
1999-11-02 16:33 ` Stephen Zander
1999-11-02 18:36   ` Randal L. Schwartz [this message]
1999-11-07  0:40     ` Lars Magne Ingebrigtsen
1999-11-08 15:46       ` Randal L. Schwartz
1999-11-11 13:18         ` Lars Magne Ingebrigtsen

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=m1zowwagg4.fsf@halfdome.holdit.com \
    --to=merlyn@stonehenge.com \
    --cc=ding@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).