Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: Always show 20 posts
Date: Mon, 31 Jul 2006 14:25:10 +0200	[thread overview]
Message-ID: <87bqr6neqh.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: <87slkigged.fsf@mail.com>

Hadron Quark <hadronquark@gmail.com> writes:

Hi Hadron,

> How to show only the last "N" read posts if "read emails or posts" are not
> displayed normally?

,----[ C-h v gnus-fetch-old-headers RET ]
| gnus-fetch-old-headers is a variable defined in `gnus-sum.el'.
| Its value is some
| 
| 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.
`----

==> 

  (setq gnus-fetch-old-headers 20)

HTH,
Tassilo
-- 
A child of five could understand this! Fetch me a child of five!

  reply	other threads:[~2006-07-31 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 11:31 Hadron Quark
2006-07-31 12:25 ` Tassilo Horn [this message]
     [not found] ` <mailman.4683.1154348731.9609.info-gnus-english@gnu.org>
2006-07-31 12:45   ` Hadron Quark

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=87bqr6neqh.fsf@baldur.nicundtas.de \
    --to=heimdall@uni-koblenz.de \
    /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).