Gnus development mailing list
 help / color / mirror / Atom feed
From: dsg@world.std.com (David S. Goldberg)
Subject: Re: [Q] primary / secondary methods differences
Date: 22 May 2001 18:28:18 -0400	[thread overview]
Message-ID: <m1bd791ow71.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <m34rud1iap.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "22 May 2001 12:04:24 -0400")


> Prefixes are already configurable, and should remain so.  I can't
> remember how I did it, but I got rid of the prefixes for groups on my
> secondary server.  Unless you subscribe to the same group on multiple
> servers, this doesn't introduce ambiguity.

Yes, but only for display.  Unless something's changed (I admit I
haven't tried this since I think it was quassia days)
gnus-group-jump-to-group, gcc headers et al require the fully prefixed
name, which I found to be confusing when the display didn't show the
prefixes.  I went back to the default display after I wanted to jump
to a group on one of three different servers and couldn't remember
which server it was on :-)
-- 
Dave Goldberg
dsg@world.std.com


  reply	other threads:[~2001-05-22 22:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 10:10 Didier Verna
2001-05-22 11:15 ` Kai Großjohann
2001-05-22 13:13   ` Didier Verna
2001-05-22 15:08     ` Kai Großjohann
2001-05-22 16:04       ` Paul Jarc
2001-05-22 22:28         ` David S. Goldberg [this message]
2001-05-22 16:10       ` Didier Verna
2001-05-22 16:20         ` Paul Jarc
2001-05-22 16:34           ` Didier Verna
2001-05-22 17:11             ` Paul Jarc
2001-05-22 17:25               ` Didier Verna
2001-05-22 22:12             ` Simon Josefsson
2001-05-23  9:39               ` Kai Großjohann
2001-05-22 16:38         ` Kai Großjohann

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=m1bd791ow71.fsf@blackbird.mitre.org \
    --to=dsg@world.std.com \
    /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).