Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Agent add servers twice?
Date: Mon, 29 Dec 2003 17:23:40 -0600	[thread overview]
Message-ID: <uy8svfbsz.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <ilubrpr1ejy.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Notice that the server is "news.gmane.org" and not
>> "nntp:news.gmane.org" which I would expect.  I'm replacing all such
>> occurrences with the fully qualified server name now and checking if
>> it helps...

This behavior is due to the agent using server names, rather than
methods, to keep track of the agentized servers.  As you noted, your
configuration provided a server name that was not fully qualified so
the agent used it.

> This helped.  To another agent problem:
>
> The agent add/remove commands in the server buffer are confused.
>
> Starting situation:
>
>      {nntp:news.nada.kth.se} (opened)
>
> That is my native server, i.e.:
>
>  '(gnus-select-method (quote (nntp "news.nada.kth.se" (nntp-address "localhost") (nntp-port-number 1191))))
>
> I press J a:
>
> Entered nntp:news.nada.kth.se into the Agent
>
>      {nntp:news.nada.kth.se} (opened)
>
> Notice no (agent)
>
> I press J a again and get
>
> Entered nntp:news.nada.kth.se into the Agent
>
>      {nntp:news.nada.kth.se} (opened) (agent)
>
> Now the lib/servers file contain:
>
> ("nntp:news.nada.kth.se" "native")
>
> Bad...

Interesting, this is further evidence of problems with the method/name
mapping.  I made changes to that code this morning (29 Dec).  Have you
updated to the latest CVS since then?

Kevin




  reply	other threads:[~2003-12-29 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 20:53 Simon Josefsson
2003-12-29 21:05 ` Simon Josefsson
2003-12-29 21:48   ` Simon Josefsson
2003-12-29 23:23     ` Kevin Greiner [this message]
2003-12-29 23:41       ` Simon Josefsson
2003-12-30  3:52         ` Kevin Greiner

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=uy8svfbsz.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).