Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Using nnrss very actively
Date: Thu, 16 Oct 2008 15:18:04 +0200	[thread overview]
Message-ID: <87fxmwof03.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <m3vdvsd79x.fsf@quimbies.gnus.org>

On Thu, 16 Oct 2008 15:00:26 +0200, Lars wrote:

> I've grown tired of mousing around in Firefox to read RSS feeds, so I
> thought I'd switch to nnrss.  I've added a few feeds, but hitting `g'
> can get kinda slow when you've added 20 feeds.  So I'd put them on a
> higher level, but then they don't really get updated until I say so,
> which kinda sucks.

> So how do all y'all use nnrss daily?

I use a script that fetches the feeds once an hour (by cron), and Gnus
just reads the fetched files.

I think it is described in the documentation, and there is a function to
create the script?

,----[ RSS ]
| `nnrss-use-local'
|      If you set `nnrss-use-local' to `t', `nnrss' will read the feeds
|      from local files in `nnrss-directory'.  You can use the command
|      `nnrss-generate-download-script' to generate a download script
|      using `wget'.
`----

The next thing is then that parsing the fetched files still seems slow
to me, but I guess that is an elisp-optimization task.


  Best regards,

    Adam

-- 
 "I always liked songs with parentheses in the title."        Adam Sjøgren
                                                         asjo@koldfront.dk




  parent reply	other threads:[~2008-10-16 13:18 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
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 [this message]
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=87fxmwof03.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).