Gnus development mailing list
 help / color / mirror / Atom feed
From: NAGY Andras <nagya@inf.elte.hu>
Subject: server connection while offline and naming servers in the agent
Date: Thu, 08 Aug 2002 19:11:20 +0200	[thread overview]
Message-ID: <dzcu1m5qnrb.fsf@mamut.elte.hu> (raw)

My server buffer looks like:

     {nntp:quimby.gnus.org} (offline) (agent)
     {nndraft:} (opened)
     {nntp:news} (offline) (agent)
     {nnml:mail} (opened)

Despite this, there is a connection to the server nicknamed `news'
(really ludens.elte.hu).

Proc         Status   Buffer         Tty         Command
----         ------   ------         ---         -------
nntpd	     open      *server ludens.elte.hu nntp  *nntpd** (none) (network stream connection to ludens.elte.hu)


Why?


----

Another issue:  in the above server buffer, I've just added
nntp:quimby.gnus.org to the agent.  However, my News/agent/lib/servers
looks like:

((nntp "quimby.gnus.org") "nntp:news")


Note the inconsistency on the naming scheme: (xy "zz") vs "xy:zz".
I've been told that the latter is better because it's some kind of
`reference name', and naming all my select methods this way avoids
duplicate connections, which arise because (xy "zz")-style select
methods are treated differently.  I've just noticed however, that my
quimby newsgroups still have select methods like `(nntp
"quimby.gnus.org")', because this is what gnus-group-make-group or
gnus-group-browse-foreign-server created.  I think that all this
hassle with multiple ways for naming (not describing) a select method,
duplicate server entries in the server buffer because of this, using
the `not recommended' scheme by default in group creation functions
just sucks.  This should be clarified and fixed.



Andras



             reply	other threads:[~2002-08-08 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 17:11 NAGY Andras [this message]
2002-12-29 23:24 ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 17:10 NAGY Andras

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=dzcu1m5qnrb.fsf@mamut.elte.hu \
    --to=nagya@inf.elte.hu \
    /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).