From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: News scan on startup vs 'g' in group buff
Date: Mon, 21 Oct 2013 17:30:45 -0400 [thread overview]
Message-ID: <87bo2inwfu.fsf@newsguy.com> (raw)
I probably should know how to find this for myself, but really don't
have a clue.
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.
next reply other threads:[~2013-10-21 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 21:30 Harry Putnam [this message]
2013-10-22 6:54 ` Glyn Millington
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=87bo2inwfu.fsf@newsguy.com \
--to=reader@newsguy.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).