Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: News scan on startup vs 'g' in group buff
Date: Sat, 26 Oct 2013 14:10:16 -0400	[thread overview]
Message-ID: <877gczdhtj.fsf@newsguy.com> (raw)
In-Reply-To: <87eh7ddcdi.fsf@nowhere.org>

Glyn Millington <glyn.millington@gmail.com> writes:

[...]

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

I'm not sure if you're asking me this, or asking for other posters to
answer.. it appears to be the same question I was asking.

What commands or functions scan for news on startup?  Is different
than `g'?

I tried evaluating that function you mentioned but got the same near
infinite stall.  But must have broke out sometime in the next half
hour because after 12 minutes I had to leave the computer... but when
I came back about half hour later it appeared to be out of the stall.

I hope that is not what does it on startup.... because as I've
mentioned, and odd though it seems.  A restart will get all groups
refreshed with no apparent giant pause or stall, whereas
 gnus-get-unread-articles or gnus-group-get-new-news goes into a very
long stall.

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

No, I haven't keep different levels for yrs, and it would take some
serious rearranging to try that.

-------        ---------       ---=---       ---------      -------- 

Now let me ask this a little differently.  

How might I study what happens on startup, as opposed to what happens
when pressing `g' in group mode.

Isn't there some mode where I watch the action somehow, and see what
gets called or where gnus is spending so much time?




  reply	other threads:[~2013-10-26 18:10 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
2013-10-26 18:10   ` Harry Putnam [this message]
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=877gczdhtj.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).