Gnus development mailing list
 help / color / mirror / Atom feed
From: mah@everybody.org (Mark A. Hershberger)
Subject: Re: [NNRSS]: 2 Problems
Date: Tue, 02 Mar 2004 22:41:38 -0600	[thread overview]
Message-ID: <87eksav8xp.fsf@weblog.localhost> (raw)
In-Reply-To: <plop87smgqkij1.fsf@gnu-rox.org> (Xavier Maillard's message of "Tue, 02 Mar 2004 23:09:54 +0100")

Xavier Maillard <zedek@gnu-rox.org> writes:

> First, one problem, the documentation says to use 'G R' to create a
> nnrss group but it fails. The workaround is to use 'G m' instead and
> answer to all the questions. Note that the problem is also referenced
> at http://www.emacswiki.org/cgi-bin/wiki?GnusRss.

I'm using 'G R' and it works (on 5.10.2).  I'll look at how it acts
with later versions (esp. CVS).

> Secondly, I quite often in the train (so not connected at all) and I
> think it would be cool if 1) gnus wouldn't complain if can't get the
> feed 2) if I could agentize nnrss. Dunno if it is possible at all.

I need help agentizing nnrss -- I don't know where to begin.

But you can make nnrss look at local files instead of the network for
its RSS.  To do this, put:

    (setq nnrss-use-local t)

in your .gnus file.  Now, get an empty buffer and type:

    M-x nnrss-generate-download-script RET

This will generate a script.  Before you leave for work (or whatever)
run the script and it'll download all the feeds.  You should be able
to read on the train then.

Mark.

-- 
Peace is only better than war if peace isn't hell, too.
    -- Walker Percy, "The Second Coming"




  reply	other threads:[~2004-03-03  4:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 22:09 Xavier Maillard
2004-03-03  4:41 ` Mark A. Hershberger [this message]
2004-03-03 21:38   ` Xavier Maillard
2004-03-03  7:31 ` Xavier Maillard
2004-03-03 12:10 ` mailla
2004-03-05  6:33 ` Kai Grossjohann
2004-03-06 15:11   ` Xavier Maillard
2004-03-10 19:28     ` [SOLVED] (was: [NNRSS]: 2 Problems) Xavier Maillard
2004-09-16 15:14 [NNRSS]: 2 problems Xavier Maillard
2004-09-16 21:02 ` Mark A. Hershberger
2004-09-18 17:38   ` Xavier Maillard

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=87eksav8xp.fsf@weblog.localhost \
    --to=mah@everybody.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).