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: Sat, 12 Feb 2005 10:45:29 -0600	[thread overview]
Message-ID: <uekflu3py.fsf@vignette.com> (raw)
In-Reply-To: <cud95f$4cb$1@sea.gmane.org>

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)))
>>> `----
>>>
>>> But still only articles which are less than 100 lines get downloaded
>>> when typing `J s'.  Isn't it supposed to work like this, or do I have
>>> to customize something else?
>>
>> That should have been sufficient. 
>>
>> 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

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.

Kevin



  reply	other threads:[~2005-02-12 16:45 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 [this message]
2005-02-12 17:50       ` Ralf Angeli
2005-02-13 18:26         ` 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=uekflu3py.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).