Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Help: Multiple News servers.
Date: 24 Feb 1996 08:44:12 +0100	[thread overview]
Message-ID: <w8senrl6ucz.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: Shane Holder's message of Fri, 23 Feb 1996 16:30:48 -0600

Shane Holder <holder@convex.com> writes:

> The next thing I found was the Server edit buffer, and after a few
> attempts, I was able to connect to cindy, and rodman, and get a list
> of groups to subscribe to.  Both servers are set up as follows with
> differing port numbers.
> 
>    (nntp "Mr_T" (nntp-port-number 8888))
> 
> I'd rather use the secondary select method for these other servers,
> but I can't figure out how to get a list of news groups, the news
> group stuff seems to only apply to gnus-select-method.

Well, this all depends a bit on what your `gnus-read-active-file' and
`gnus-check-new-newsgroups' variables are.  If `gnus-read-active-file'
is t, then you can just plonk your virtual servers into
`gnus-seconary-select-methods' and Gnus will subscribe you (or not) to
all new groups from these servers.

If `gnus-read-active-file' is nil or `some', then you can set
`gnus-check-new-newsgroups' to a list of select methods to query for
new groups.

> I also had trouble posting to groups subscribed to with the
> browse-server stuff, I think it tried to post to the
> gnus-select-method server, and not the one I had browsed, and the
> group doesn't exist on the primary server.

Use `C-u C-c C-c' when posting to post with the same server as you
read the group from.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


      reply	other threads:[~1996-02-24  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-23 22:30 Shane Holder
1996-02-24  7:44 ` Lars Magne Ingebrigtsen [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=w8senrl6ucz.fsf@hler.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).