From: David Sumbler <david@aeolia.co.uk>
Subject: Re: Checking mail
Date: Wed, 12 Jan 2005 15:53:47 +0000 [thread overview]
Message-ID: <m3mzvemyno.fsf@ceres.staly.plus.com> (raw)
In-Reply-To: <m3d5wbeg2u.fsf@ceres.staly.plus.com>
I wrote:
> I still have the problem that when I start Gnus (or press 'g' in the
> Group buffer), it does not get new mail, although it gets new news
> and new archived messages.
>
> All of my mail and news groups currently have level 3, except for a
> couple of mailboxes which I have set to level 1 and 2.
>
> If I give a prefix to 'g' (e.g. 'C-u 5 g') then it updates the mail
> OK.
I have now discovered that nnfolder-get-new-mail is nil, although the
manual says that the default is t. I imagine that this is the cause
of the odd behaviour.
"No problem", thought I, and I added the line
(setq nnfolder-get-new-mail t)
to my .gnus file.
But it didn't work: I find that after I start Gnus,
nnfolder-get-new-mail is still nil, although the Gnus file _is_ being
read.
If I then do (setq nnfolder-get-new-mail t) in the *scratch* buffer,
then nnfolder-get-new-mail correctly shows up as t, but if I exit from
Gnus, then nnfolder-get-new-mail is again nil! Let me repeat that,
because I think it's weird: exiting Gnus changes the value of
nnfolder-get-new-mail from t to nil.
I don't understand why this is, and therefore I can't get round the
problem. But I dare say some of you experienced (Gn)users will be
able to give me a possible explanation. At least, I hope so!
David
--
prev parent reply other threads:[~2005-01-12 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3k6qwk7vl.fsf@ceres.staly.plus.com>
2005-01-02 21:13 ` Niels L. Ellegaard
[not found] ` <m3r7l21636.fsf@ceres.staly.plus.com>
[not found] ` <m3d5wbeg2u.fsf@ceres.staly.plus.com>
2005-01-12 15:53 ` David Sumbler [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=m3mzvemyno.fsf@ceres.staly.plus.com \
--to=david@aeolia.co.uk \
/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).