Re: Need suggestions for changing agent's downloadable mark.

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Simon Josefsson <jas@extundo.com> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>>>
>>>> Any idea where I could find this functionality? I thought that
>>>> gnus-update-marks (gnus-sum.el) would be appropriate as it updates the
>>>> info structure but no luck.  The same was true of
>>>> gnus-gnus-to-quic-newsrc-format (gnus-start.el).  I think that your
>>>> suggestion is reasonable, I just don't know where to start with the
>>>> implementation.
>>>
>>> gnus-adjust-marked-articles?  I don't understand why it doesn't
>>> already work, though.
>>
>> Thanks that's it.  The behavior of gnus-adjust-marked-articles is
>> determined by gnus-article-mark-to-type which returns the result of
>> looking up gnus-article-special-mark-lists.
>>
>> gnus-article-special-mark-lists's value is 
>> ((seen range)
>>  (killed range)
>>  (bookmark tuple)
>>  (score tuple))
>>
>> So, all I need to do is add (download list) or (download range) to it.
>
> If download is a list, it shouldn't be added to
> gnus-article-special-mark-lists.  Only non-list mark list types should
> be added.  See the definition of gnus-article-mark-to-type.
>
> (gnus-article-mark-to-type 'downloadable)
>  => list

Hmmm.  Are lists unsorted or, at least, not sorted by ascending numeric value?

I think that range is better but someone wrapped ALL of the range
logic in a cond block that is only true for the mark seen.  Was that
correct?  Shouldn't we trim killed and bookmark marks as they go outside
of the active range?

Kevin