Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Bastien <bzg@altern.org>
To: anhnmncb <anhnmncb@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: How to speed up the nnrss rechieving? Too slow!
Date: Fri, 29 Feb 2008 11:03:21 +0000	[thread overview]
Message-ID: <877igo2feu.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86zltkp5bk.fsf@freebsd.hasee.cpu> (anhnmncb@gmail.com's message of "Fri, 29 Feb 2008 15:52:47 +0800")

anhnmncb <anhnmncb@gmail.com> writes:

> I have tried, set all nnrss group to level 4 and start gnus by emacs
> -eval '(gnus 3)'
> now every nnrss group starts with *, 
>        *: nnrss:Gentoo Linux News
>        *: nnrss:FreshPorts news
> it need me to go to every  group and type RET to see it, not friendly
> too much :(

Maybe what you need here is "Gnus Topics":

,----[ (info "(gnus)Group Topics") ]
| If you read lots and lots of groups, it might be convenient to group
| them hierarchically according to topics.  You put your Emacs groups over
| here, your sex groups over there, and the rest (what, two groups or so?)
| you put in some misc section that you never bother with anyway.  You can
| even group the Emacs sex groups as a sub-topic to either the Emacs
| groups or the sex groups--or both!  Go wild!
`----

Since all your RSS feeds are already downloaded by the script, you can
just leave the RSS groups at their initial level (say, "3") and put them
in a folded topic.

-- 
Bastien

      parent reply	other threads:[~2008-02-29 11:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 13:13 anhnmncb
2008-02-28 14:00 ` Bastien
2008-02-28 15:07   ` Bastien
2008-03-03  7:14     ` William Xu
2008-03-03  8:16       ` Bastien
2008-03-03  9:08         ` William Xu
2008-03-03  9:32           ` Bastien
2008-03-03  9:59             ` William Xu
2008-03-04 14:43       ` William Xu
     [not found]     ` <mailman.8203.1204528522.18990.info-gnus-english@gnu.org>
2008-03-03  7:57       ` anhnmncb
2008-03-03 15:15         ` William Xu
     [not found]         ` <mailman.8238.1204557624.18990.info-gnus-english@gnu.org>
2008-03-03 16:15           ` anhnmncb
2008-03-04  2:35             ` William Xu
2008-03-10  5:05       ` RSS should use Group Timestamps jidanni
     [not found]       ` <mailman.8631.1205125567.18990.info-gnus-english@gnu.org>
2008-03-10 13:29         ` Ted Zlatanov
     [not found]   ` <mailman.8039.1204211245.18990.info-gnus-english@gnu.org>
2008-02-29  0:16     ` How to speed up the nnrss rechieving? Too slow! anhnmncb
2008-02-29  2:47       ` William Xu
     [not found]       ` <mailman.8064.1204253412.18990.info-gnus-english@gnu.org>
2008-02-29  6:21         ` anhnmncb
2008-02-29  9:06           ` William Xu
     [not found] ` <mailman.8033.1204207257.18990.info-gnus-english@gnu.org>
2008-02-29  7:52   ` anhnmncb
2008-02-29  9:09     ` William Xu
     [not found]     ` <mailman.8073.1204276215.18990.info-gnus-english@gnu.org>
2008-02-29 10:19       ` anhnmncb
2008-02-29 11:03     ` Bastien [this message]

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=877igo2feu.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=anhnmncb@gmail.com \
    --cc=info-gnus-english@gnu.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).