From: Elias Oltmanns <eo@nebensachen.de>
To: ding@gnus.org
Subject: Re: Canonical server names and the false assumption in g-s-named-server
Date: Fri, 09 Nov 2007 14:15:20 +0100 [thread overview]
Message-ID: <87r6izlfvb.fsf@denkblock.local> (raw)
In-Reply-To: <87ejgytey1.fsf@denkblock.local>
Elias Oltmanns <eo@nebensachen.de> wrote:
[...]
> For these reasons I suggest to apply the patch attached below. Actually,
> I'd prefer to have gnus-agent-covered-methods store methods rather than
> servers, but I suppose that this will introduce more problems with
> existing installations upgrading to the next release of gnus.
As for the ChangeLog entry, I'm not quite sure in what format to provide
it to make it easier for you to import. Anyway, here it goes:
* gnus.el (gnus-method-to-server): Add an optional parameter so the
caller can indicate whether the cache should be disregarded for this
call. This way the result of the call is reproducible at all times and
can be considered a canonical server name for the supplied method.
(gnus-agent-method-p): Canonicalize server names by pushing their method
through (gnus-method-to-server) using the newly added no-cache
parameter.
* gnus-srvr.el (gnus-server-insert-server-line): Use the new no-cache
parameter of gnus-method-to-server for the gnus-named-server property.
Regards,
Elias
prev parent reply other threads:[~2007-11-09 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 15:11 Shouldn't agentised servers be switched offline in unplugged mode? Elias Oltmanns
2007-09-16 22:37 ` Canonical server names and the false assumption in g-s-named-server (was: Shouldn't agentised servers be switched offline in unplugged mode?) Elias Oltmanns
2007-11-09 13:15 ` Elias Oltmanns [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=87r6izlfvb.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=ding@gnus.org \
/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).