From: Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com>
Subject: Re: gnus-demon-scan-mail problems
Date: Fri, 20 Jun 2003 13:33:47 +0200 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87ptl9q8ys.fsf@gothgoose.net> (raw)
In-Reply-To: <ur85sk6m3.fsf@gnu.org>
* Sam Steingold <sds@gnu.org> wrote:
>> (setq gnus-use-demon t)
> this variable is not mentioned in the gnus sources.
Uhm, yes, you are right. I removed this variable. I found this code
somewhere on the web, copied it to my gnus setup and it worked from the
beginning. Hm, has there ever been a gnus-use-demon variable in older
versions of Gnus?
>> (defun gnus-demon-scan-news ()
>> (when (gnus-alive-p)
>> (save-excursion
>> (set-buffer gnus-group-buffer)
>> (gnus-group-get-new-news))))
>>
>> (gnus-demon-add-handler 'gnus-demon-scan-news 5 10)
>>
>> (gnus-demon-init)
>
> `gnus-demon-add-handler' already calls `gnus-demon-init'.
Yes, you are right again. :-) After checking gnus-demon.el I also
removed this code from my setup.
> now, how do you know that there was new mail?
> do you visit the *Group* buffer every 10 minutes?
Well, after being done with reading mails and news I just switch back to
the group buffer and do other stuff. And if new mails/news arrive the
group buffer will be automatically updated.
> `gnus-demon-scan-news' does no notification!
Well, seeing that new postings arrived in my group buffer is enough
notification for me. Having a sound alert might be a nice feature though.
Regards,
Marcus
--
"Intentions not up front and the shit that never faced reflects the sliver of
God's face and looped a flaw rotates forever unresolved. Sure to die.
I'll think about that."
prev parent reply other threads:[~2003-06-20 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <un0girkzn.fsf@gnu.org>
2003-06-16 19:24 ` Marcus Frings
[not found] ` <ur85sk6m3.fsf@gnu.org>
2003-06-20 11:33 ` Marcus Frings [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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87ptl9q8ys.fsf@gothgoose.net \
--to=iam-est-hora-surgere@fuckmicrosoft.com \
--cc=protagonist@gmx.net \
/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).