Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Excessive nntp reads since today
Date: Wed, 05 Sep 2012 19:36:41 +0200	[thread overview]
Message-ID: <87vcfsv0ba.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <857gs874qu.fsf@iznogoud.viz> (Wolfgang Jenkner's message of "Wed, 05 Sep 2012 19:34:49 +0200")

Wolfgang Jenkner <wjenkner@inode.at> writes:

>>>> Then the docs were wrong:
>>>>
>>>> ,----[ C-h v gnus-fetch-old-headers RET ]
>>>> | gnus-fetch-old-headers is a variable defined in `gnus-sum.el'.
>>>> | 
>>>> | Documentation:
>>>> | [...] If it has the value `some', all old headers will be fetched but
>>>> | only enough headers to connect otherwise loose threads will be
>>>> | displayed. [...]
>>>> `----
>>>>
>>>> Wolfgang fixed the implementation to reflect exactly what the docs
>>>> say.  IMHO, we'd better have fixed the docs and let the
>>>> implementation as it has been.
>>>
>>> Yeah, but that's after the clarification.  :-)  They used to say:
>>>
>>> -displayed in the Summary buffer.  If this variable is t, Gnus
>>> -will attempt to grab the headers to the old articles, and thereby
>>> -build complete threads.  If it has the value `some', only enough
>>> -headers to connect otherwise loose threads will be displayed.  This
>>> -variable can also be a number.  In that case, no more than that number
>>> -of old headers will be fetched.  If it has the value `invisible', all
>>>
>>> i.e., it didn't say that all headers would be fetched...
>>
>> Oh, Wolfgang, you prankster. ;-)
>
> ???  I think you are misunderstanding.

Indeed.

> As I said, that clarification was made in 2005-11-20 by Kevin Greiner.

Ok, ok.  My suggestion stands as-is anyway.

Bye,
Tassilo



      reply	other threads:[~2012-09-05 17:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:11 Tassilo Horn
2012-06-12 13:11 ` Wolfgang Jenkner
2012-06-12 13:36   ` Tassilo Horn
2012-06-12 14:35     ` Wolfgang Jenkner
2012-06-12 15:56       ` Wolfgang Jenkner
2012-06-12 16:31       ` Tassilo Horn
2012-06-13 13:48         ` Wolfgang Jenkner
2012-06-13 15:18           ` Tassilo Horn
2012-06-13 16:36             ` Wolfgang Jenkner
2012-06-13 18:57               ` Tassilo Horn
2012-06-16 11:37                 ` Wolfgang Jenkner
2012-06-16 12:53                   ` Tassilo Horn
2012-06-16 14:18                     ` Wolfgang Jenkner
2012-09-05 13:56         ` Lars Ingebrigtsen
2012-09-05 14:38           ` Tassilo Horn
2012-09-05 16:19             ` Lars Ingebrigtsen
2012-09-05 17:16               ` Tassilo Horn
2012-09-05 17:34                 ` Wolfgang Jenkner
2012-09-05 17:36                   ` Tassilo Horn [this message]

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=87vcfsv0ba.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=larsi@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).