Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: Re: nnslashdot - quickref quide please
Date: 06 Dec 1999 14:54:03 -0500	[thread overview]
Message-ID: <76puwjsv50.fsf@ppllc.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "05 Dec 1999 23:13:05 +0100"

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

    KG> They do different things altogether.  It's like asking whether an
    KG> automatic gear shift is easier than power steering and whether the
    KG> two go hand in hand...

Great analogy!  Thanks for putting that into perspective!

    KG> By adding nnslashdot to the secondary select methods or via the
    KG> server buffer, you enable Gnus to access the groups.  The topic-based
    KG> approach works with both and tells Gnus where to put newly-discovered
    KG> nnslashdot groups.

I chose to add nnslashdot to my secondary selection methods and to switch my
gnus-subscribe-newsgroup-method from gnus-subscribe-zombies to
gnus-subscribe-topics.  The question I have now is what happens to my new
non-nnslashdot groups?  They used to show up as zombies but now I'm just not
sure.  Should they show up under my Gnus topic and not in any of my other
subtopics?  So far, none have shown and I don't know if that's because there
truly aren't any new ones of if because there is a problem.

Thanx!


-- 
Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza II                           Beeper: (800) 505-2795
Jersey City, NJ 07311                  E-mail: colman@ppllc.com
                                       E-mail: jcolman@jnc.com
                                          web: http://www.ppllc.com

"Every time I think I've idiot-proofed something someone comes up with a
better idiot"


  reply	other threads:[~1999-12-06 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-16 22:38 Jake Colman
1999-11-16 22:44 ` Kai Großjohann
1999-12-01 15:38 ` Lars Magne Ingebrigtsen
1999-12-01 23:42   ` Jake Colman
1999-12-05 22:13     ` Kai Großjohann
1999-12-06 19:54       ` Jake Colman [this message]
1999-12-06 22:39         ` Kai Großjohann
1999-12-07  3:53           ` Jack Vinson
1999-12-07 18:39             ` dave-mlist
1999-12-08  4:25             ` Jake Colman
1999-12-08  5:29               ` Jack Vinson
1999-12-10 11:27             ` Peter Makholm

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=76puwjsv50.fsf@ppllc.com \
    --to=colman@ppllc.com \
    --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).