Re: I lied (Was: Group-specific gnus-auto-select-next?)

[Lloyd Zusman <ljz@asfast.com>]

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

> Lloyd Zusman <ljz@asfast.com> writes:
> 
>> What follows at the end of this message is the code for
>> `gnus-summary-read-group'.  Notice the 10th line of that function,
>> where `gnus-auto-select-next' is set to nil in the `let' block.  This
>> causes any and all changes to the value of `gnus-auto-select-next'
>> from within `gnus-summary-read-group-1' to get undone after that
>> function returns.
> 
> This seems to be a bad thing, and IWBNI some other way could be
> devised to achieve the same effect.
> 
> Why is gnus-auto-select-next bound to nil, anyway?

I'm going to make a wild guess as to why: perhaps it's set to nil to
avoid problems if the group being read by `gnus-summary-read-group' is
empty at the time that function is being invoked.

But whatever the case, I agree with you that there probably would be
other ways to achieve the intended effect of the temporary binding of
`gnus-auto-select-next' to nil, whatever that intended effect might
be.


> Thanks for being willing to work on this.

Tonight or tomorrow I'll experiment with this routine, to see if I can
determine the intention of binding `gnus-auto-select-next' to nil, and
if so, then to see if I can devise a different way to achieve this
intention.

For now, I have to go to work ... <sigh>


> kai
> -- 
> Abort this operation?   [OK]  [Cancel]


-- 
 Lloyd Zusman
 ljz@asfast.com