Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: M-g on a group moves to next group
Date: 05 Mar 1999 11:02:01 -0500	[thread overview]
Message-ID: <glmzp5sylfq.fsf@caffeine.mitre.org> (raw)
In-Reply-To: Jason L Tibbitts III's message of "04 Mar 1999 13:01:39 -0600"

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.
  




  reply	other threads:[~1999-03-05 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-04 17:37 Dmitry Yaitskov
1999-03-04 17:53 ` Kai.Grossjohann
1999-03-04 19:01 ` Jason L Tibbitts III
1999-03-05 16:02   ` Justin Sheehy [this message]
1999-03-05 17:06     ` Jason L Tibbitts III
1999-03-05 18:32       ` Justin Sheehy
     [not found]   ` <x7k8wxxb6x.fsf@chow.mat.jhu.edu>
1999-03-05 17:17     ` Dan Christensen
1999-03-04 19:05 ` Justin Sheehy
1999-03-04 19:19   ` Alan Shutko
1999-03-04 19:38     ` Dmitry Yaitskov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=glmzp5sylfq.fsf@caffeine.mitre.org \
    --to=justin@linus.mitre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).