Gnus development mailing list
 help / color / mirror / Atom feed
From: Sudish Joseph <sj@eng.mindspring.net>
Subject: Re: Gnus and NoCeM.
Date: 19 Jul 1999 13:53:10 -0400	[thread overview]
Message-ID: <yviag12kttkp.fsf@ra.eng.mindspring.net> (raw)
In-Reply-To: Colin Rafferty's message of "15 Jul 1999 16:27:19 -0400"

Colin Rafferty writes:
>> One question, though.  Do I still have to set gnus-use-nocem?  

> Yes.

[ Apologies if I misunderstood the question. ]

AFAIK, once the daemon is initialized, gnus-use-nocem can be nil,
allowing purely asynch operation.  Here's what I use:

;; NoCem
(setq gnus-use-nocem t
      gnus-nocem-groups '("news.lists.filters"
                          "news.admin.net-abuse.bulletins"
                          "news.admin.net-abuse.announce"))

;; daemons
(setq gnus-use-demon t)
(gnus-demon-add-handler 'gnus-demon-scan-nocem   30 10)
[...]
(gnus-demon-init)
(setq gnus-use-nocem nil)

I'm almost certain that setting gnus-use-nocem to t before setting the 
nocem demon handler is unnecessary, but I haven't been motivated to
see if I can remove it.


The only other demon I use is this one, which causes incoming mail to
be split when my XEmacs is otherwise idle.  Very useful if you get
lots of incoming mail and you do not want to wait on "g."  Note that
it assumes that all mail groups are level 2 or better.

(gnus-demon-add-handler 'sj/gnus-demon-scan-news 20 5)
(defun sj/gnus-demon-scan-news ()
  (when (gnus-alive-p)
    (save-window-excursion
      (save-excursion
        (set-buffer gnus-group-buffer)
        (gnus-group-get-new-news 2)))))


-- 
Sudish Joseph                                          MindSpring Enterprises


  parent reply	other threads:[~1999-07-19 17:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-15 17:59 Ken McGlothlen
1999-07-15 19:05 ` Colin Rafferty
1999-07-15 19:32   ` Ken McGlothlen
1999-07-15 20:27     ` Colin Rafferty
1999-07-15 21:51       ` Ken McGlothlen
1999-07-15 22:58         ` David Hedbor
1999-07-16  0:15       ` Dan Christensen
1999-07-17  3:54         ` Justin Sheehy
1999-07-17  7:02           ` Ugh! Ack! Argh! Nggh! Ken McGlothlen
     [not found]             ` <wtnu2r3bslp.fsf@licia.dtek.chalmers.se>
1999-07-17 10:15               ` Hans de Graaff
1999-07-17 16:05                 ` Michael Cook
1999-07-17 10:17               ` Kjetil Ødegaard
1999-07-17 11:02               ` Kai Großjohann
1999-07-17 12:21                 ` Harry Putnam
1999-07-17 11:14             ` Kai Großjohann
1999-07-18  7:10               ` Ken McGlothlen
1999-07-19 10:50                 ` Kai Großjohann
1999-07-27 15:37                   ` Jack Vinson
1999-07-26 17:14                     ` Hrvoje Niksic
1999-07-26 17:45                       ` Paul Stevenson
1999-07-26 17:50                         ` Paul Stevenson
1999-07-26 19:13                         ` François Pinard
1999-07-28 12:15                         ` Robert Bihlmeyer
1999-07-28 14:38                           ` Paul Stevenson
1999-07-17 10:58           ` Gnus and NoCeM Kai Großjohann
1999-07-19 17:53       ` Sudish Joseph [this message]
1999-07-15 20:49     ` Justin Sheehy
1999-07-16  4:50     ` Andrew Hobson
1999-07-16  5:37       ` Ken McGlothlen
1999-07-16 14:02         ` Jack Twilley
1999-07-15 21:32 ` Kai Großjohann
1999-07-16 15:28 ` Wes Hardaker

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=yviag12kttkp.fsf@ra.eng.mindspring.net \
    --to=sj@eng.mindspring.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).