Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Altering maximum article download size for agent
Date: Sun, 13 Feb 2005 12:26:21 -0600	[thread overview]
Message-ID: <uhdkguxiq.fsf@vignette.com> (raw)
In-Reply-To: <culfi2$7e4$1@sea.gmane.org>

Ralf Angeli <dev.null@iwi.uni-sb.de> writes:

> * Kevin Greiner (2005-02-12) writes:
>
>> Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
>>
>>> * Kevin Greiner (2005-02-09) writes:
>>>
>>>> Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
>>>>
>>>>> ,----[ ~/News/agent/lib/categories ]
>>>>> | ((default short nil nil))
>>>>> | ((default (agent-length-when-short . 150) (agent-predicate . short)))
>>>>> `----
> [...]
>>>> What do you get when you do the following in the group buffer?
>>>>
>>>> M-: (gnus-agent-find-parameter "group-name-as-displayed-in-group-buffer" 'agent-short-article)
>>>>
>>>> It should return your 150.
>>>
>>> Unfortunately not:
>>>
>>> 100 (0144, 0x64)
>>>
>>>> What does this return?
>>>> M-: (gnus-get-predicate (gnus-agent-find-parameter "group-name-as-displayed-in-group-buffer" 'agent-predicate))
>>>
>>> gnus-agent-short-p
>
> Addendum to the above: My primary select method is nnnil and I don't
> have a standard group line, so I used both the full name
> (e.g. nntp+news.gmane.org:gmane.emacs.gnus.general) and the short name
> (e.g. gmane.emacs.gnus.general) for those tests which both returned
> the same values.
>
>> Nothing unfortunate. The gnus-agent-find-parameter function checks for
>> group parameters before your category parameter.  Try this, open your
>> group then enter 'M-x c-e' to edit group parameters.  I believe that
>> you'll find the 100 there.
>
> Sorry, I don't understand that key sequence.  But I think the output of
> `M-: (gnus-group-find-parameter "nntp+news.gmane.org:gmane.emacs.gnus.general" 'agent-short-article t) RET'
> would do as well.  This is nil.
>
> Stepping through `gnus-agent-find-parameter' I saw that the call to
> `gnus-group-parameter-value' returns nil as well.
>
> And after stepping through `gnus-group-parameter-value' I think it
> would work if 'agent-short-article and 'agent-length-when-short would
> not be different symbols.  In that case the `(eq (car elem) symbol)'
> test in `gnus-group-parameter-value' would return t and the function
> would return the value of 150 specified in the categories file.
>
> Checking ...
>
> `M-: (gnus-agent-find-parameter "nntp+news.gmane.org:gmane.emacs.gnus.general" 'agent-length-when-short) RET'
>
> 150 (0226, 0x96)

You are absolutely correct.  It also looks like I made the same
mistake with the long article attribute, possibly others as well.  I'm
going to need a couple of days, rather busy right now and I'd like to
look back over the history to refresh why the code ended up looking
like this.

Kevin



      reply	other threads:[~2005-02-13 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 12:49 Ralf Angeli
2005-02-09 13:01 ` Kevin Greiner
2005-02-09 15:12   ` Ralf Angeli
2005-02-12 16:45     ` Kevin Greiner
2005-02-12 17:50       ` Ralf Angeli
2005-02-13 18:26         ` 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=uhdkguxiq.fsf@vignette.com \
    --to=kevin.greiner@vignette.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).