Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Plaksin <happy@usg.edu>
To: ding@gnus.org
Subject: Re: Using nnrss very actively
Date: Mon, 20 Oct 2008 13:13:58 -0400	[thread overview]
Message-ID: <wsmygzw5nt.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <87zll45oiw.fsf@randomsample.de>

David Engster <deng@randomsample.de> writes:

> "Robert D. Crawford" <rdc1x@comcast.net> writes:
>
>> Mark Plaksin <happy@mcplaksin.org> writes:
>>
>>> But wait!  You *do* want to program something.  nnrss doesn't deal
>>> with ATOM feeds so what you really want to do is write nngreader :)
>>> g-client from Emacspeak has some of the work done already.  I started
>>> working on nngreader for myself a while back haven't had time to touch
>>> it lately.
>>
>> One solution is to try this:
>>
>> $WGET -q -O "$RSSDIR"/'Planet Emacsen.xml' 'http://planet.emacsen.org/atom.xml' 
>> cd /home/rdc/News/rss
>> mv Planet\ Emacsen.xml Planet\ Emacsen.temp.xml 
>> xsltproc -o Planet\ Emacsen.xml /home/rdc/share/emacs/site-lisp/emacspeak/xsl/atom2rss.xsl Planet\ Emacsen.temp.xml
>>
>> works, and that is really all that matters until gnus supports atom.  
>
> For people who don't use these wget scripts, one can also defadvice
> mm-url-insert to call xsltproc:
>
> http://www.randomsample.de/dru5/node/8

These methods look cool and I'll try them.

Another problem that I have on and off with nnrss is having it show me
old articles.  I have this problem both when I use an external script to
fetch the feeds and when I don't.  I've tried to figure it out and there
have been threads on this list about it but I've never found a perfect
solution.

Do others have this problem too?  I haven't updated my CVS Emacs or Gnus
in a few months so maybe the problem is gone now.




  reply	other threads:[~2008-10-20 17:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 13:00 Lars Magne Ingebrigtsen
2008-10-16 13:15 ` David Engster
2008-10-16 13:27   ` Lars Magne Ingebrigtsen
2008-10-16 13:43     ` David Engster
2008-10-16 13:52       ` Lars Magne Ingebrigtsen
2008-10-16 16:27         ` Mark Plaksin
2008-10-16 17:15           ` Lars Magne Ingebrigtsen
2008-10-17  8:45             ` Paul R
2008-10-17  8:57               ` David Engster
2008-10-17  9:18                 ` Paul R
2008-10-17 14:00             ` Andreas Seltenreich
2008-10-16 17:46           ` Robert D. Crawford
2008-10-16 19:27             ` David Engster
2008-10-20 17:13               ` Mark Plaksin [this message]
2008-10-21 15:53                 ` Ted Zlatanov
2008-10-21 16:24                 ` Adam Sjøgren
2008-10-28  0:04                 ` Mark Plaksin
2008-10-28  5:20                   ` Andreas Seltenreich
2008-10-28 12:11                     ` Mark Plaksin
2008-10-31  8:00                       ` nnrss-ignore-article-fields for more than just fields jidanni
2008-10-31 17:39                         ` Ted Zlatanov
2008-11-10 22:04                           ` Ted Zlatanov
2008-11-11  7:37                             ` Reiner Steib
2008-11-11 14:38                               ` Ted Zlatanov
2008-11-19 22:41                             ` Adam Sjøgren
2008-11-20 16:40                               ` Ted Zlatanov
2008-10-16 13:17 ` Using nnrss very actively Robert D. Crawford
2008-10-16 13:18 ` Adam Sjøgren
2008-10-18 23:10 ` Sebastian Krause
2008-10-18 23:16 ` Kevin Ryde
2008-10-20 20:20   ` Lars Magne Ingebrigtsen
2008-10-21 15:56     ` Ted Zlatanov
2008-10-25  0:03     ` Kevin Ryde
2008-11-03 23:43       ` Content-Location for w3m display (was: Using nnrss very actively) Kevin Ryde

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=wsmygzw5nt.fsf@stone.tss.usg.edu \
    --to=happy@usg.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).