Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Some agent whining (again)
Date: Tue, 15 Apr 2003 19:02:58 -0500	[thread overview]
Message-ID: <uu1cz2tsd.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <hv7k9vvogw.fsf@rasputin.ws.nextra.no>

Bjørn Mork <bmork@dod.no> writes:

> This may be unjustified, and basically my own fault, but I need to let
> it out anyway...
>
> I am sitting here offline, like I do a few times a year. And facing
> the same problem I feel I have each and every time: I have (stupidly?)
> kept updating to the latest and greatest CVS Gnus to get all the new
> and shiny features, and somehow along the way it seems that the agent
> has stopped working. Of course, as usual I have also been stupid
> enough not to test it before going offline.
>
> This time it seems that the default category somehow mysteriously has
> changed predicate from short to false.

The change was an accident.  The predicate for every new category
EXCEPT for 'default' is false.

The predicate for the 'default' category has been changed back to
short.  However, you won't notice it unless you delete your
agent/lib/categories file again.  If you don't want to do that, you'll
have to edit the predicate in the category.

> Well, that's easy to change but
> is breaking existing configurations really necessary?

Absolutely.  How else can we gain your appreciation except to patch the
errors that we previously introduced :).

> And how much
> configuraton is an user expected to do just to use Agent? 

I do believe that configurability is a cornerstone of gnus.

That being said, the default should match the documentation.

>And why
> can't I find this change mentioned in GNUS-NEWS?

The default category is stored, along with all other agent categories,
in agent/lib/categories.  Those categories override the internal
default so most people, including myself, didn't trigger the branch of
the code that you apparently traversed.

> I'm finished now. Pleas excuse the noise.
 
No problem.  Please accept the response with the appropriate jest.

BTW, the patch has been checked in.

Kevin



      reply	other threads:[~2003-04-16  0:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 14:12 Bjørn Mork
2003-04-16  0:02 ` Kevin Greiner [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=uu1cz2tsd.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).