Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnslashdot usage
Date: Tue, 11 Dec 2001 10:39:45 +0100	[thread overview]
Message-ID: <vafelm2rt7i.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <81wuzwoxan.fsf@zion.bpnetworks.com> (Ami Fischman's message of "Sun, 09 Dec 2001 14:15:12 -0800")

Ami Fischman <usenet@fischman.org> writes:

> Hi -- curious to hear how people are using nnslashdot.  Following the
> manual, I am able to browse the slashdot server, and subscribe to topics as
> groups, and then read them.  However, this seems clunky to me (possibly b/c
> I've only done it three times now :)).  What seems more aligned with Gnus'
> current situation is to have ONE group for nnslashdot, which got new topics
> as articles, and the followup posts to the topic would be threaded under the
> initial topic article.

But the solution you want seems to be difficult to implement, as
ShengHuo says.

You might get closer to what you want by using topic subscriptions:
create a topic for nnslashdot and arrange all new nnslashdot groups to
be subscribed under that topic.  Then you can open or close the topic
in the *Group* buffer and it will not be as visually disturbing.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



  parent reply	other threads:[~2001-12-11  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 22:15 Ami Fischman
2001-12-10 17:36 ` ShengHuo ZHU
2001-12-10 19:07   ` Ami Fischman
2001-12-10 19:41     ` ShengHuo ZHU
2001-12-11 20:43   ` Ami Fischman
2001-12-11  9:39 ` Kai Großjohann [this message]
2001-12-11 17:34   ` Ami Fischman
2001-12-29  0:55 ` Lars Magne Ingebrigtsen
2001-12-29  2:21   ` ShengHuo ZHU
2001-12-29  2:34     ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1999-11-11 19:30 Bruce Z. Lysik
1999-11-11 21:47 ` Shenghuo ZHU
1999-11-11 22:00   ` Laura Conrad
1999-11-11 22:06   ` Bruce Z. Lysik

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=vafelm2rt7i.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).