prefix arg of RET not same as entering number of articles?

prefix arg of RET not same as entering number of articles?

[Kai Großjohann]

My Gnus group contains 600 ticked old articles plus a few new ones.
I've set gnus-large-newsgroup to 500 and gnus-fetch-old-headers also
to 500.  gnus-build-sparse-threads is nil, the default value I think.

I've discovered that hitting RET on the group then answering 99 to the
prompt is not the same thing as typing 9 9 RET!  I had previously
expected these two to do the same thing and was about to set
gnus-large-newsgroup to a nearly infinite value.

Suppose there is one unread message.  I hit RET, then answer 99 to the
prompt.  I see 98 of the ticked message, plus the unread one.  If,
however, I hit 9 9 RET, I see the 99 most recent messages, whether
they are ticked or marked as read or expirable.

Do I have to set gnus-large-newsgroup to 0 or is there some other way
to get both behaviors even for small groups?

kai
-- 
Life is hard and then you die.

Re: prefix arg of RET not same as entering number of articles?

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> I've discovered that hitting RET on the group then answering 99 to the
> prompt is not the same thing as typing 9 9 RET!

No, they're quite different.

> Suppose there is one unread message.  I hit RET, then answer 99 to the
> prompt.  I see 98 of the ticked message, plus the unread one.  If,
> however, I hit 9 9 RET, I see the 99 most recent messages, whether
> they are ticked or marked as read or expirable.

Yup.

> Do I have to set gnus-large-newsgroup to 0 or is there some other way
> to get both behaviors even for small groups?

I thing you have to set that variable to 0 to get the behavior.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen