From: Joseph Barillari <jbarilla@princeton.edu>
Cc: ding@gnus.org
Subject: Re: Noobish question: why doesn't nnrss display anything?
Date: Thu, 08 May 2003 20:52:26 -0400 [thread overview]
Message-ID: <87y91hrlf9.fsf@bigbox.barillari.org> (raw)
In-Reply-To: <87smrp5clc.fsf@batman.everybody.org> (Mark A. Hershberger's message of "Thu, 08 May 2003 16:54:07 -0500")
>>>>> "MAH" == Mark A Hershberger <mah@everybody.org> writes:
MAH> Joseph Barillari <jbarilla@princeton.edu> writes:
>> If I hit `B <ret> nnrss <ret>', I get the nnrss URL prompt.
MAH> You've hit a bug. That method doesn't work as expected.
MAH> Try "G R url RET" in the *Group* buffer instead.
Thanks. That took care of the subscription problem, but another one
arose:
As suggested in http://my.gnus.org/Lisp/1031707976, I have (setq
nnrss-use-local t) in my .gnus. I used nnrss-generate-download-script
to generate a shell-script to fetch the feeds, and I have a cron job
that runs that shell script. The shell script works.
The trouble is that nnrss doesn't update the .el files corresponding
to the .xml files when I hit `g' to get new news. It's clearly doing
_something_ with them, for `g' takes a few seconds with the nnrss
groups subscribed (rather than a fraction of a second if I unsubscribe
from them).
Result: the .xml files have new articles, the .el files have old
articles, and so do the summary buffers for the group.
Any suggestions on how I might diagnose this?
Thanks in advance,
--Joe
>> P.S.: If Shenghuo Zhu is on this list, please accept my compliments for
>> implementing another reason to never leave gnus.
MAH> FWIW, I've done most of the recent work on nnrss. And I'm probably to
MAH> blame for this breakage.
Regardless of the breakage, thanks for the code. It's a very cool idea.
--
Joseph Barillari -- http://barillari.org
next prev parent reply other threads:[~2003-05-09 0:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 14:34 Joseph Barillari
2003-05-08 21:54 ` Mark A. Hershberger
2003-05-09 0:52 ` Joseph Barillari [this message]
2003-05-11 23:00 ` Alex Schroeder
2003-05-12 0:52 ` Mark A. Hershberger
2003-05-12 18:53 ` Alex Schroeder
2003-05-12 19:37 ` Mark A. Hershberger
2003-05-12 20:35 ` Alex Schroeder
2003-05-12 21:02 ` Mark A. Hershberger
2003-05-12 22:55 ` Alex Schroeder
2003-05-13 3:14 ` Mark A. Hershberger
2003-05-20 8:29 ` nnrss.el Alex Schroeder
2003-10-18 13:25 ` nnrss.el Lars Magne Ingebrigtsen
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=87y91hrlf9.fsf@bigbox.barillari.org \
--to=jbarilla@princeton.edu \
--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).