From: David Moore <dmoore@UCSD.EDU>
Subject: Re: BUG: NoCeM and foreign groups: does it work?
Date: 24 Jul 1997 12:08:01 -0700 [thread overview]
Message-ID: <rvlo2wgtf2.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: roth@cse.ucsc.edu's message of "23 Jul 1997 17:03:57 -0700"
roth@cse.ucsc.edu (Carl D. Roth) writes:
> 1. gnus-nocem-scan-groups seems incapable of scanning for NoCeM in
> foreign groups. That is, virtual group names in the NoCeM/active
> file have the undesired effect of scanning the local version of
> the group instead.
>
> This sounds like a stupid point, but my local news server doesn't
> carry all of the NoCeM bulletin groups.
>
I use the following to scan some foreign groups at a slightly less
frequent rate than normal local groups. Since it works, it suggests
that foreign groups work also. Actually, i have news.zippo.com as a
secondary server, if that makes a difference.
(gnus-demon-add-nocem)
(gnus-demon-add-handler 'dmoore::gnus-demon-scan-nocem-zippo 120 t)
(defun dmoore::gnus-demon-scan-nocem-zippo ()
(let ((gnus-nocem-groups
(mapcar (lambda (x) (concat "nntp+news.zippo.com:" x))
gnus-nocem-groups))
(nntp-nov-is-evil nil))
(save-window-excursion
(gnus-nocem-scan-groups)
;; FIX FIX FIX why is this nntp:... ?
(gnus-close-server "nntp:news.zippo.com"))))
> 3. The real deficiency is in how gnus-nocem-enter-article decides
> when a message-id should enter the nocem cache. Basically, unless
> one of the groups mentioned in the nocem article matches a
> locally-subscribed group, the scan will miss.
>
> I noticed this problem because I orthogonally set up my newsrc so
> that *all* groups are foreign... I watched nocem run for about a
> week without matching a single article!
>
> The way I've worked around points 1. and 3. above is to slightly
> modify gnus-nocem-enter-article to match groups out of a *different*
> hashtb than gnus-newsrc-hashtb. This new hash table consists of the
> gnus-group-real-name mappings of all of the groups in the newsrc.
> This way, the nocem groups match up, and I can start accumulating
> message-ids.
yeah, something like this is a good idea.
--
David Moore <dmoore@ucsd.edu> | Computer Systems Lab __o
UCSD Dept. Computer Science - 0114 | Work: (619) 534-8604 _ \<,_
La Jolla, CA 92093-0114 | Fax: (619) 534-1445 (_)/ (_)
<URL:http://oj.egbt.org/dmoore/> | In a cloud bones of steel.
next prev parent reply other threads:[~1997-07-24 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-24 0:03 Carl D. Roth
1997-07-24 0:30 ` Raja R Harinath
1997-07-24 19:08 ` David Moore [this message]
1997-07-25 0:27 ` Carl D. Roth
1997-07-25 18:50 ` Lars Magne Ingebrigtsen
1997-07-25 19:33 ` Carl D. Roth
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=rvlo2wgtf2.fsf@sdnp5.ucsd.edu \
--to=dmoore@ucsd.edu \
/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).