From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: automatic Agentizing of servers (was: Summary buffer
Date: Tue, 25 Nov 2003 09:25:00 +0100 [thread overview]
Message-ID: <ilufzgcyhwj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <uptfhrwns.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 24 Nov 2003 20:48:07 -0600")
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Mon, 24 Nov 2003, kgreiner@xpediantsolutions.com wrote:
>>
>>> The highlighting should only occur if you have both enabled the
>>> agent (now the default) AND agentized the servers. If you are
>>> truely using the latest version of gnus from CVS, you may have been
>>> effected by the latest bug fix. The agent had a bug whereby editing
>>> a method's configuration could result in it being unagentized.
>>> That's because the agent was failing to find an exact match when it
>>> compared the old and new methods. It gets to be a rather long story
>>> but the patch prevents, and corrects, this sort of problem. So, if
>>> the old gnus unagentized some of your servers then the new gnus
>>> could have reversed that error to make then agentized again.
>>
>> I have the agent enabled (gnus-agent is t). No servers were agentized
>> when I quit Gnus. My nnimap server was agentized when I started Gnus.
>> I would like to keep gnus-agent t, without automatic agentizing of any
>> of my servers. I have not edited any server method configurations.
>>
>> I use the latest CVS, updated nightly, and I made sure I was up to
>> date before restarting Gnus.
>
> I've traced this behavior to the gnus-agent-auto-agentize-methods
> variable. If you don't agentize ANY server, the methods named in this
> variable (currently nntp and nnimap) will be agentized by gnus when
> you start up. Perhaps we can make this customizable or only apply it
> when the agent is being used for the first time (for example, when
> agent/lib/servers doesn't exist). I'd rather defer this to the
> original author since I'm not aware of the requirements behind adding it.
The variable was added to behave as you suggest it should. The code
says (gnus-agentize):
(unless gnus-agent-covered-methods
(mapc
(lambda (server-or-method)
(let ((method (gnus-server-to-method server-or-method)))
(when (memq (car method)
gnus-agent-auto-agentize-methods)
(push (gnus-method-to-server method)
gnus-agent-covered-methods)
(setq gnus-agent-method-p-cache nil))))
(cons gnus-select-method gnus-secondary-select-methods))))
And gnus-agent-covered-methods should be read from
~/News/agent/lib/servers. So only when g-a-c-m is nil should the auto
agentizing happen. Hm. I guess if you deagentize all your servers,
they would be auto-agentized again. But if no servers are agentized,
what's the point if using the agent? Perhaps it should disable itself
in that case.
next prev parent reply other threads:[~2003-11-25 8:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 15:14 Summary buffer highlighting Emerick Rogul
2003-11-24 16:17 ` automatic Agentizing of servers (was: Summary buffer highlighting) Ted Zlatanov
2003-11-24 16:42 ` automatic Agentizing of servers (was: Summary buffer Emerick Rogul
2003-11-24 16:47 ` Kevin Greiner
2003-11-24 17:05 ` Emerick Rogul
2003-11-24 17:07 ` Ted Zlatanov
2003-11-25 2:48 ` Kevin Greiner
2003-11-25 8:25 ` Simon Josefsson [this message]
2003-11-25 18:31 ` Ted Zlatanov
2003-12-29 21:22 ` Steinar Bang
2003-12-29 21:39 ` Simon Josefsson
2003-12-29 21:58 ` Steinar Bang
2003-12-29 22:23 ` Steinar Bang
2003-12-29 22:27 ` Steinar Bang
2003-12-29 22:36 ` Steinar Bang
2003-12-29 22:33 ` Simon Josefsson
2003-12-29 22:44 ` Steinar Bang
2003-12-29 23:00 ` Simon Josefsson
2003-12-29 23:10 ` Kevin Greiner
2003-12-29 23:17 ` Simon Josefsson
2003-12-29 23:37 ` Kevin Greiner
2003-12-29 23:53 ` Simon Josefsson
2003-12-30 2:19 ` Harry Putnam
2003-12-30 9:44 ` Steinar Bang
2003-12-30 11:16 ` Simon Josefsson
2003-12-30 20:55 ` Steinar Bang
2003-12-30 21:30 ` Simon Josefsson
2003-12-30 22:49 ` Harry Putnam
2003-12-31 12:55 ` Steinar Bang
2003-12-30 9:40 ` Steinar Bang
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=ilufzgcyhwj.fsf@latte.josefsson.org \
--to=jas@extundo.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).