M-g on a group moves to next group

M-g on a group moves to next group

[Dmitry Yaitskov]

Subj. Seems counterintuitive (sp?) to me. I do M-g on a group to
update that group, and most probably to read it afterwards... or is
there a way to check for new articles without moving? Thanks.

-- 
Cheers,
-Dima.

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

[Kai.Grossjohann]

M-g moves in case you want to fetch new mail for several groups.
kai
-- 
I like _\bb_\bo_\bt_\bh kinds of music.

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

[Jason L Tibbitts III]

>>>>> "DY" == Dmitry Yaitskov <dimas@home.com> writes:

DY> Seems counterintuitive (sp?) to me. I do M-g on a group to update
DY> that group, and most probably to read it afterwards... or is there a
DY> way to check for new articles without moving? Thanks.

I can understand why it would be confusing, but I can also understand why
it moves, since I often do both operations (fetch new news in a group, then
enter it and fetch new news for several groups in sequence).

What I would really like to do is automatically fetch new news in a group
every time it is entered.  I'd also like to have an rn-like option to fetch
new news just as you're about to leave a group.  (N new articles have
arrived while you were reading; read them now?)  And while I'm dreaming,
short key sequences to get straight to new news in my inbox and other
important groups from wherever I happen to be.

I know that most of this can be done with hooks (and the hotkey group
switch with what should be short functions) but lisp is completely swapped
out of my wetware right now.  Has anyone achieved any of these?

 - J<

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

[Justin Sheehy]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> M-g moves in case you want to fetch new mail for several groups.

Huh?  I use M-g (gnus-topic-get-new-news-this-topic) constantly.  For
me, it does not move to the next group.  If it did, I'd need to
redefine it back to its current useful behavior.

There are plenty of other good ways to check mail for several groups
at once.

-- 
Justin Sheehy

In a cloud bones of steel.
  

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

[Alan Shutko]

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

J> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
>> M-g moves in case you want to fetch new mail for several groups.

J> Huh?  I use M-g (gnus-topic-get-new-news-this-topic) constantly.
J> For me, it does not move to the next group.

You're both right.

gnus-goto-next-group-when-activating's value is 
t

Documentation:
*If non-nil, the M-g command will advance point to the next group.

You can customize this variable.

Defined in `gnus-group'.



-- 
Alan Shutko <ats@acm.org> - By consent of the corrupted
Fine day to work off excess energy.  Steal something heavy.

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

[Dmitry Yaitskov]

Alan Shutko <ats@acm.org> spake thusly:

> >>>>> "J" == Justin Sheehy <justin@linus.mitre.org> writes:
> 
> J> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> >> M-g moves in case you want to fetch new mail for several groups.
> 
> J> Huh?  I use M-g (gnus-topic-get-new-news-this-topic) constantly.
> J> For me, it does not move to the next group.
> 
> You're both right.
> 
> gnus-goto-next-group-when-activating's value is 
> t
> 
> Documentation:
> *If non-nil, the M-g command will advance point to the next group.
> 
> You can customize this variable.
> 
> Defined in `gnus-group'.

I see. Thanks.

-- 
Cheers,
-Dima.

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

[Justin Sheehy]

Jason L Tibbitts III <tibbs@math.uh.edu> writes:

> What I would really like to do is automatically fetch new news in a group
> every time it is entered. 

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

If you really didn't want it to only work for one keybinding, you
could advise gnus-group-select-group, but I wouldn't recommend that.

> I'd also like to have an rn-like option to fetch new news just as
> you're about to leave a group.

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

> And while I'm dreaming, short key sequences to get straight to new
> news in my inbox and other important groups from wherever I happen
> to be.

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

One thing that I've done is define two sets of group-entry keys.  One
of them enters the group in the manner that I normally view groups,
with scoring, threading, etc.  Well, I didn't do anything for these.
These are just the ones that I didn't rebind.

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

-- 
Justin Sheehy

In a cloud bones of steel.
  

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

[Jason L Tibbitts III]

>>>>> "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<

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

[Dan Christensen]

[I meant to send this to the list, since it contains a recommendation
for a change to Gnus, but had actually just sent it to Jason.]

Jason L Tibbitts III <tibbs@math.uh.edu> writes:
> I'd also like to have 
> ...
> short key sequences to get straight to new news in my inbox and other
> important groups from wherever I happen to be.

You could use something like what I've attached below.  I think the
third function, which prompts for a group name (with completion) and
selects that group, would be a useful addition to Gnus.  I have it
bound to `J' in both the *Group* and *Summary* buffers, and I use it
all the time.

Dan

; move point to the line in the group buffer containing my inbox
(defun jdc-gnus-group-jump-to-inbox ()
  (interactive)
  (gnus-group-jump-to-group "nnfolder:Inbox"))

; select my inbox
(defun jdc-gnus-group-select-inbox (&optional all)
  (interactive "P")
  (gnus-group-read-group all t "nnfolder:Inbox"))

; select an arbitrary group; something like this would be
; great to have as part of Gnus.
(defun jdc-gnus-group-select-a-group (group &optional all)
  "Select newsgroup GROUP.
Interactively, query for group name with completion.
No article is selected automatically.
If ALL is non-nil, already read articles become readable.
If ALL is a number, fetch this number of articles."

  (interactive
   (list (completing-read
	  "Group: " gnus-active-hashtb nil
	  (gnus-read-active-file-p)
	  nil
	  'gnus-group-history)
	 current-prefix-arg))

  (when (equal group "")
    (error "Empty group name"))

  (gnus-group-read-group all t group))

(global-set-key [f11 ?i] 'jdc-gnus-group-select-inbox)

(add-hook 'gnus-group-mode-hook
'(lambda ()
   (define-key gnus-group-mode-map "/" 'jdc-gnus-group-jump-to-inbox)
   (define-key gnus-group-mode-map "J" 'jdc-gnus-group-select-a-group)
   (define-key gnus-group-mode-map "i" 'jdc-gnus-group-select-inbox)))

(add-hook 'gnus-sum-load-hook 
'(lambda nil
   (define-key gnus-summary-mode-map "J" 'jdc-gnus-group-select-a-group)
   (define-key gnus-summary-mode-map "i" 'jdc-gnus-group-select-inbox)
))

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

[Justin Sheehy]

Jason L Tibbitts III <tibbs@math.uh.edu> 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?

Hm.  I don't know.  What I was suggesting was to write a function that
did both the get-new-news and the select-group parts, and rebinding
your group entry key to that function.

Something roughly like:

(defun your-group-entry ()
       (interactive)
       (gnus-group-get-new-news-this-group)
       (gnus-group-select-group))

and then bind some key to your-group-entry.  Subsequently, using that
key to enter groups could also get new news for them.

I doubt that function is exactly what you want; I only intended it to
show the general idea that I was referring to.

-- 
Justin Sheehy

In a cloud bones of steel.