Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Agent Customization check-in
Date: Sun, 02 Mar 2003 19:06:56 -0600	[thread overview]
Message-ID: <uvfz1i7gv.fsf@xpediantsolutions.com> (raw)

Just to let everyone know, I just finished a rather large check-in. 

If you download individual files, the following files should be
downloaded together because their modifications are cross-dependent.

  gnus-agent.el, gnus-art.el, gnus-cus.el, gnus-int.el

Also, gnus-start.el is dependent on a change in gnus-util.el.

The new features are:
* Agent parameters are now merged with group/topic parameters.  This
  means that you can customize agent behavior at the individual group
  level.
* Agent categories (which are still supported) now have a
  customization buffer.  The 'e' command in the category buffer will
  display it.
* The precidence rule for parameters is in decending order: group
  parameter, topic parameter, category parameter, defined constant.
* A new agent parameter has been added.  It enables/disables agent
  expiration per individual group.
* The gnus-agent-cache feature, which did not appear to function per
  the documentation, has been re-implemented.  When gnus-agent-cache
  is cleared (i.e. nil), the plugged agent will always fetch from the
  server.
* You can now configure gnus to write .newsrc.eld directly to disk.
  It is considerably slower than saving a temporary buffer but can
  prevent memory exhaustion errors.

Kevin



             reply	other threads:[~2003-03-03  1:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03  1:06 Kevin Greiner [this message]
2003-03-03  1:50 ` Katsumi Yamaoka
2003-03-03  2:42   ` 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=uvfz1i7gv.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).