Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: C y on really large groups
Date: Wed, 11 May 2011 16:47:23 -0500	[thread overview]
Message-ID: <87oc38x638.fsf@lifelogs.com> (raw)
In-Reply-To: <muxhb9162ez.fsf@uzeb.lrde.epita.fr>

On Wed, 11 May 2011 10:56:36 +0200 Didier Verna <didier@xemacs.org> wrote: 

dvl>        Got it. The problem is that I have gnus-auto-expirable-newsgroups
dvl> set to ".*". When doing a catchup, Gnus grabs the article range which is
dvl> something like (min . max) and maps over all the actual numbers in order
dvl> to add the expirable mark on each article. So no wonder it takes hours.

dvl> What's more intriguing is that this variable is not supposed to affect
dvl> nntp groups so I hadn't expected this behavior. But now that I think of
dvl> it, I realize that all my nntp newsgroups articles have the E mark set
dvl> (I can see that in the summary buffers), which does really make sense,
dvl> does it ?

You can set the E mark, but since the backend is read-only (there's a
nn* variable for this) it won't matter.  So the code on catchup that
adds the E mark should simply check the backend and skip processing if
the E mark is irrelevant.

Ted




  reply	other threads:[~2011-05-11 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 14:44 Didier Verna
2011-05-10 15:40 ` Adam Sjøgren
2011-05-10 16:01   ` Tassilo Horn
2011-05-10 16:09     ` Adam Sjøgren
2011-05-10 19:57       ` Tassilo Horn
2011-05-10 16:16     ` Antoine Levitt
2011-05-11  7:53       ` Didier Verna
2011-05-11  8:15         ` Didier Verna
2011-05-11  8:19           ` Didier Verna
2011-05-11  8:56             ` Didier Verna
2011-05-11 21:47               ` Ted Zlatanov [this message]
2011-05-30 20:06                 ` Lars Magne Ingebrigtsen

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=87oc38x638.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).