From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Avoid opening secondary select methods as foreign servers
Date: Tue, 03 Aug 2010 14:10:47 -0500 [thread overview]
Message-ID: <877hk7cy14.fsf@lifelogs.com> (raw)
In-Reply-To: <87eif1kgtt.fsf@topper.koldfront.dk>
On Sat, 17 Jul 2010 22:13:02 +0200 asjo@koldfront.dk (Adam Sjøgren) wrote:
AS> On Wed, 07 Jul 2010 01:57:11 +0200, Adam wrote:
>> This patch changes gnus-secondary-select-method-p to only look at
>> the first two elements in the list (nntp and "news.server.org"),
>> because the incoming argument never has the entire list.
>> gnus-check-server is then changed to call gnus-secondary-select-method-p
>> and if the server in question is in secondary-select-methods, the
>> configuration from there is used.
>> ---
>> lisp/gnus-int.el | 3 +++
>> lisp/gnus.el | 6 +++---
>> 2 files changed, 6 insertions(+), 3 deletions(-)I
AS> I get the feeling that I've become Warnocked¹ here.
AS> Anyone want to comment on the approach in the patch?
AS> I have been using it since I posted it, to no ill effect.
AS> I did have "nntp:news.gmane.org" for some groups in my .newsrc.eld, and
AS> (nntp "news.gmange.org") for others; changing the former to the latter
AS> stopped Gnus complaining about posting to possible unknown groups.
It seems OK to me but I haven't seen the problem you are fixing so I
can't verify it works. Has anyone? Can you explan how to trigger the bug?
Ted
next prev parent reply other threads:[~2010-08-03 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 20:51 Setting gnus-check-new-newsgroups to nil --> gnus-secondary-select-methods ignored Adam Sjøgren
2010-07-06 20:58 ` Adam Sjøgren
2010-07-06 23:57 ` [PATCH] Avoid opening secondary select methods as foreign servers Adam Sjøgren
2010-07-17 20:13 ` Adam Sjøgren
2010-08-03 19:10 ` Ted Zlatanov [this message]
2010-08-08 13:59 ` Adam Sjøgren
2010-08-08 14:14 ` Adam Sjøgren
2010-08-09 14:12 ` Ted Zlatanov
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=877hk7cy14.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).