Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Goldberg <david.goldberg6@verizon.net>
Subject: Re: problem with nnrss and slashdot
Date: Tue, 08 Aug 2006 22:52:44 -0400	[thread overview]
Message-ID: <x78xlytybn.fsf@davestoy.homelinux.org> (raw)
In-Reply-To: <m3ac6gakph.fsf@kurono.home> (joakim@verona.se's message of "Mon,	07 Aug 2006 12:44:58 +0200")

>>>>> On Mon, 07 Aug 2006 12:44:58 +0200, joakim@verona.se said:

> joakim@verona.se writes:
>> I recently upgraded gnus, and now the rss feed from slashdot get new
>> copies everytime i update the group. Any hints?

> This problem remains. Is there anything I can do to help debug it?
> Specifically I'm having problems with the slashdot rss feed.

Just yesterday I decided to give gnus a try as an rss reader and
slashdot was one of my test cases.  I see the same behavior as above.
However, I don't see it with a couple other feeds.  I also took a look
at the changelogs and nnrss doesn't seem to have changed in some time.
Assuming it did work correctly once, I suspect that slashdot has made
some change that gnus is not prepared for.

Also, I also gave nnslashdot a try but that has the articles all in
html which I find painful as I avoid html mails in general and when I
do I filter through lynx which no longer seems to work properly on
cygwin.  Is there a better way to render html in XEmacs on cygwin?  I
tried w3m many moons ago but had trouble getting it to configure and
compile.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net




  reply	other threads:[~2006-08-09  2:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 10:51 joakim
2006-06-21 15:15 ` Mark Plaksin
2006-08-07 10:44 ` joakim
2006-08-09  2:52   ` Dave Goldberg [this message]
2006-08-09 12:43     ` Mark Plaksin
2006-08-10  6:42       ` joakim
2006-08-10 20:01         ` David Hansen
2006-08-09 22:16     ` Dave Goldberg

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=x78xlytybn.fsf@davestoy.homelinux.org \
    --to=david.goldberg6@verizon.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).