Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Glyn Millington <glyn.millington@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Using things from 'custom.el'
Date: Thu, 27 Mar 2014 06:57:22 +0000	[thread overview]
Message-ID: <87r45oqgbx.fsf@nowhere.org> (raw)
In-Reply-To: <8761n0pkdd.fsf@talktalk.net>

Sharon Kimble <boudiccas@talktalk.net> writes:

> gnus-fetch-old-headers

C-h v is your friend

,----
| Documentation:
| *Non-nil means that Gnus will try to build threads by grabbing old headers.
| If an unread article in the group refers to an older, already
| read (or just marked as read) article, the old article will not
| normally be 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', all
| old headers will be fetched but 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
| old headers will be fetched, but none will be displayed.
| 
| The server has to support NOV for any of this to work.
| 
| This feature can seriously impact performance it ignores all
| locally cached header entries.  Setting it to t for groups for a
| server that doesn't expire articles (such as news.gmane.org),
| leads to very slow summary generation.
`----

atb




Glyn



  reply	other threads:[~2014-03-27  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27  0:15 Sharon Kimble
2014-03-27  6:57 ` Glyn Millington [this message]
2014-03-27 15:15 ` Michael Heerdegen

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=87r45oqgbx.fsf@nowhere.org \
    --to=glyn.millington@gmail.com \
    --cc=info-gnus-english@gnu.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).