Re: M-g on a group moves to next group

[Jason L Tibbitts III <tibbs@math.uh.edu>]

>>>>> "JS" == Justin Sheehy <justin@linus.mitre.org> writes:

JS> Just rebind whatever key you use for group entry to do
JS> gnus-group-get-new-news-this-group before its usual function.

Is gnus-select-group-hook early enough to do this?  I can never tell from
the docs precisely when the hooks are called.  Just adding
gnus-group-get-new-news-this-group there doesn't seem to help.

JS> I mean, it's easy to do a gnus-summary-rescan-group by hand, but doing
JS> the sort of prompting that you refer to would actually require a little
JS> bit of work.

I know; I wonder if it would be possible to wedge into
gnus-exit-group-hook.  Check to see if the number of unread articles is
zero (i.e. you read everything) then get-new-news-this-group, then check if
unread articles are still zero and exit if not, prompt if so.  Perhaps I
should try to remember what Lisp I learned.

JS> Easy from the *Group* buffer, trickier if you want it to really be from
JS> wherever you might happen to be.  Doable, but not trivial. Especially
JS> if you want to be able to get back to where you were before you made
JS> that jump.

Dan Christensen send me some code; I've found that whenever Gnus is loaded
(which is essentially "always) I can just do

(gnus-group-read-group nil t "nnml:inbox")

But I can't seem to make it grab new news.

JS> The other will get new news for that group before entering it, turn off
JS> most of the threading and scoring stuff, and sort in reverse
JS> chronological order.  That way I am instantly reading the most-recently
JS> received message.  Some of the time, in a few of my groups, that is
JS> exactly what I want.

I find that for groups where I want to read that way, I _always_ want to
read that way and so I set it in the group parameters.

 - J<