Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@mit.edu>
Subject: Re: no primary server !
Date: Tue, 26 Apr 2005 10:18:33 -0400	[thread overview]
Message-ID: <y68ekcxei4m.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <87d5sikpv3.fsf@koldfront.dk>

asjo@koldfront.dk (Adam Sjøgren) writes:

> At times I've sometimes found it aesthetically unpleasing that one
> server is treated different than others (naming-wise, for instance),
> but I admit that I never exerted any effort in obtaining a deep
> understanding of the issues involved.

Here I have three different backends (nnml, nntp, and nndsc, which
reads MIT's quite dated 'discuss' boards), and it was also annoying
that one of them got treated differently.  It was worse that, a long
long time ago, I set up gnus-select-method to '(nntp "news.mit.edu")
but my primary usage is mail, so the thing with the "blessed" names
only had a dozen or so interesting groups in it.

I think if you're primarily using a single backend -- probably nntp,
nnml, or nnimap -- then it makes sense to bless that as
gnus-select-method.  But if you've got several backends and multiple
servers, you get to think a little less (and, admittedly, type a
little more) if you use nnnil as your primary select method.

(My work email now has gnus-select-method as nnimap, and it's great,
aside from that my finger-macros got trained by years at MIT, so my
"refile this article" command is 'B m nnml:mail. C-backspace
C-backspace INBOX.group.name'.  :-)

  --dzm


      reply	other threads:[~2005-04-26 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24 15:49 Flatty
2005-04-25  7:12 ` Adam Sjøgren
2005-04-26  3:53   ` Ian Zimmerman
2005-04-26  5:49     ` Flatty
2005-04-26  6:34     ` Adam Sjøgren
2005-04-26 14:18       ` David Z Maze [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=y68ekcxei4m.fsf@contents-vnder-pressvre.mit.edu \
    --to=dmaze@mit.edu \
    /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).