From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: scanning for new mail with demon-handler
Date: Sun, 19 Jun 2011 20:08:07 +0200 [thread overview]
Message-ID: <8739j5n188.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <87oc1tlqa1.fsf@nzebook.haselwarter.org> (Philipp Haselwarter's message of "Sun, 19 Jun 2011 18:49:58 +0200")
Philipp Haselwarter <philipp.haselwarter@gmx.de> writes:
> On 2011-06-17 20:34 UT, lee <lee@yun.yagibdah.de> wrote:
>
> l> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>>> On Fri, 17 Jun 2011 21:05:06 +0200, lee wrote:
>>>
>>>> Yes, it does more, that´s why I like gnus-demon-scan-mail :)
>>>> Gnus-demon-scan-news also scans for new news, creating unneccessary
>>>> network traffic and load on the news servers.
>>>
>>> If you put your mail groups on a different level than your
>>> newsgroups, maybe you can use a customized version of
>>> gnus-demon-scan-news to do what you want.
>
> l> Hm, I´ve read a post saying that you could set newsgroups to a higher
> l> level for them not to be included when checking for new messages.
>
> I'd suggest something like
>
> Modified lisp/gnus-demon.el
> diff --git a/lisp/gnus-demon.el b/lisp/gnus-demon.el
>
> For example, I keep local mail on level 1, external mail on 3, nntp on 4
> and nnrss on level 5 and fetch them accordingly:
>
> #+begin_src emacs-lisp
> (gnus-demon-add-handler 'gnus-demon-scan-news-1 121 10)
> (gnus-demon-add-handler 'gnus-demon-scan-news-3 240 10)
> (gnus-demon-add-handler 'gnus-demon-scan-news-4 601 10)
> (gnus-demon-add-handler 'gnus-demon-scan-news-5 7201 10)
> #+end_src
That´s a good idea :) Any chance of this becoming the default?
BTW, since you´re setting timestamps, did you get nndiary to work? I
managed to get an "nndiary:diary" group in the group view after manually
creating the group (The documentation should point out that you need to
create the group manually ...), yet nndiary does nothing. It doesn´t
receive new mail from its source, and when I move messages manually into
the diary group, nothing happens either.
next prev parent reply other threads:[~2011-06-19 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 16:54 lee
2011-06-17 17:04 ` Adam Sjøgren
2011-06-17 19:05 ` lee
2011-06-17 19:17 ` Adam Sjøgren
2011-06-17 19:19 ` Adam Sjøgren
2011-06-17 20:34 ` lee
2011-06-19 16:49 ` Philipp Haselwarter
2011-06-19 18:08 ` lee [this message]
2011-06-19 22:07 ` Adam Sjøgren
2011-06-20 2:19 ` Philipp Haselwarter
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=8739j5n188.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--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).