Re: How to stop gnus from moving to the next group?

[Leo <sdl.web@gmail.com>]

On 2010-05-12 09:45 +0100, Andreas Seltenreich wrote:
> Leo writes:
>
>> On 2010-04-29 03:38 +0100, Leo wrote:
>>> 1. go to a group (that has a next group with unread articles)
>>> 2. C-u RET
>>> 3. When there's prompt in the minibuffer asking how many articles, hit C-g
>>
>> I dig a bit into it. It is due to gnus-summary-read-group-1 having
>> (gnus-group-next-unread-group 1) unconditionally. Should that respect
>> gnus-group-goto-unread or a new customisation variable?
>
> It does respect it, AFAICT.
> 
>> There could be a lot of empty groups between current and the next unread
>> group. The movement is undesirable in this case.
>
> I agree.  I don't think it is sensible to do anything beyond cleanup
> when catching the C-g.  After all, choosing a million articles at the
> prompt and hitting C-g while Gnus is thrashing doesn't move point
> either.

I think making C-g trigger new action is already in violation of
intuitive user expectation. Imagine if C-s move to the next occurrence
when C-g. Fortunately this doesn't occur as often as C-s. Anyway I have
fixed this locally.

> I'll push a fix into No Gnus.  In case anyone is attached to the old
> behavior: Entering 0 instead of C-g at the prompt will still move point.

As a user I find it difficult to appreciate such a subtle behaviour. I
think making it simple and intuitive will help new users a lot.

> Thanks,
> andreas

Leo