Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nntp groups downloading all headers on each entry
Date: Mon, 22 Oct 2012 18:35:24 +0800	[thread overview]
Message-ID: <871ugqu74j.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ipa39ezp.fsf@thinkpad.tsdh.de>


On 22 October 2012 14:51, Tassilo Horn <tsdh@gnu.org> wrote:

    Eric Abrahamsen <eric@ericabrahamsen.net> writes:
    
    >>> I'm still reconsituting my gnus configuration, and with my current
    >>> (still minimal) setup I'm seeing weird behavior: On each entry of an
    >>> nntp group, I'm apparently downloading *all* headers for the group
    >>> -- in
    >>
    >> Maybe check out the setting of gnus-fetch-old-headers?
    >
    > That did it! And I only had to wait 20 minutes to see your reply :)
    > Turns out it was my fault after all -- I'd set it to 'some, for
    > reasons that totally escape me.
    
    Yes, that behavior has changed recently.  Have a look at this thread.
    
      http://news.gmane.org/gmane.emacs.gnus.general/cutoff=82423
    
    I also have the value 'some for `gnus-fetch-old-headers', and now that
    means that Gnus will fetch *all* old headers initially.  But it will do
    that only once.

Only once per gnus session? That's the behavior I was seeing with 'some....




  reply	other threads:[~2012-10-22 10:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  5:39 Eric Abrahamsen
2012-10-21 14:29 ` Eric S Fraga
2012-10-22  3:40   ` Eric Abrahamsen
2012-10-22  6:51     ` Tassilo Horn
2012-10-22 10:35       ` Eric Abrahamsen [this message]
2012-10-22 11:56         ` Tassilo Horn
2012-10-22 13:08           ` Eric Abrahamsen
2012-10-23  6:23             ` Tassilo Horn
2012-10-23  7:05               ` Eric Abrahamsen

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=871ugqu74j.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).