From: James Cloos <cloos@jhcloos.com>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Localized rescan (M-g)
Date: Mon, 04 Jul 2011 12:57:19 -0400 [thread overview]
Message-ID: <m3mxgukmpk.fsf@jhcloos.com> (raw)
In-Reply-To: <87d3hrc6xx.fsf@newsguy.com> (Harry Putnam's message of "Sun, 03 Jul 2011 17:53:14 -0500")
>>>>> "HP" == Harry Putnam <reader@newsguy.com> writes:
HP> In my setup I notice that whenever I do a localized rescan on a
HP> single group gnus scrolls to the next group on completion.
HP> That doesn't make much sense does it?
I find that I repeat M-g to update a block of groups quite frequently.
A quick look at the source for gnus-group-get-new-news-this-group
led me to the variable gnus-goto-next-group-when-activating:
,----[ C-h v gnus-goto-next-group-when-activating RET ]
| gnus-goto-next-group-when-activating is a variable defined in `gnus-group.el'.
| Its value is t
|
| Documentation:
| *If non-nil, the M-g command will advance point to the next group.
|
| You can customize this variable.
|
| [back]
`----
So, customize that to null if you do not want M-g to go the the next group.
(I ran C-h k M-g in the *Group* buffer to get the help for the M-g command,
moved to point to the underlined _gnus-group.el_ in the resulting *Help*
buffer. That opened gnus-group.el with point at the start of the function
gnus-group-get-new-news-this-group. I then scrolled to the end of that
function to see whether the point move was conditionalized, where I found
gnus-goto-next-group-when-activating. C-h v gave the above info.)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2011-07-04 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 22:53 Harry Putnam
2011-07-04 9:55 ` Steinar Bang
2011-07-05 13:48 ` Harry Putnam
2011-07-04 16:57 ` James Cloos [this message]
2011-07-05 13:48 ` Harry Putnam
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=m3mxgukmpk.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
--cc=reader@newsguy.com \
/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).