From: Glyn Millington <glyn.millington@gmail.com>
To: ding@gnus.org
Subject: Re: News scan on startup vs 'g' in group buff
Date: Tue, 22 Oct 2013 07:54:17 +0100 [thread overview]
Message-ID: <87eh7ddcdi.fsf@nowhere.org> (raw)
In-Reply-To: <87bo2inwfu.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> When gnus starts from scratch, something that scans for 'news' must be
> called, I want to know if that call is different than the command
> gnus-group-get-new-news' that is called with 'g' in group buffer?
>
> Why I ask is that I've had a problem for a good while now where
> calling 'g' ( `gnus-group-get-new-news' ) times out and unless you
> have some kind of timeout setup, its a good minute wait. Then you
> aren't sure if all groups got refreshed or what.
>
> My usual work-around is to use M-g on a topic:
> gnus-topic-get-new-news-this-topic' or even more fine grained by using
> M-g' on a specific group or a pile of process marked groups.
>
> But a moments thought will tell you that leaves a lot undone that the
> g' command would have taken care of.
>
> One (last ditch) work-around is to restart gnus, which even though it
> must call some kind of news scan it does not timeout.
>
> A poor thing to have to do to get what one can usually do with 'g'.
>
> Since I'm way less skilled than my near multiple decade use of gnus
> would indicate and if no one has any advice on how to track down what
> is causing the time out, then I thought finding out why a restart
> doesn't time out, that is, what is different scanning for news during
> start up compared to 'g' then maybe I could just use that bit for now
> as a work-around.
Is it by any chance gnus-get-unread-articles ?
On your 'g' problem, a quick look at the docstring for
gnus-group-get-new-news, opens up at least one possibility
,----
| (gnus-group-get-new-news &optional ARG ONE-LEVEL)
|
| Get newly arrived articles.
| If ARG is a number, it specifies which levels you are interested in
| re-scanning. If ARG is non-nil and not a number, this will force
| "hard" re-reading of the active files from all servers.
| If ONE-LEVEL is not nil, then re-scan only the specified level,
| otherwise all levels below ARG will be scanned too.
`----
Have you tried passing a numerical argument to 'g' ? ie 'C-u 2 g', if
your mail groups are at level 2 and 1?
hth
Glyn
next prev parent reply other threads:[~2013-10-22 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 21:30 Harry Putnam
2013-10-22 6:54 ` Glyn Millington [this message]
2013-10-26 18:10 ` Harry Putnam
2013-10-26 18:47 ` Glyn Millington
2013-10-26 22:41 ` Harry Putnam
2013-10-27 6:28 ` Glyn Millington
2013-10-27 15:07 ` Harry Putnam
2013-10-29 23:58 ` Dan Christensen
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=87eh7ddcdi.fsf@nowhere.org \
--to=glyn.millington@gmail.com \
--cc=ding@gnus.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).