Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: unoder.spam@spam.jay.net (Martin Jørgensen)
Subject: Re: a couple of newbie questions with gnus
Date: Wed, 31 May 2006 05:10:57 +0200	[thread overview]
Message-ID: <13evk3-qk6.ln1@news.tdc.dk> (raw)
In-Reply-To: <mailman.2439.1149011220.9609.info-gnus-english@gnu.org>

Tassilo Horn <heimdall@uni-koblenz.de> writes:

> unoder.spam@spam.jay.net (Martin Jørgensen) writes:
-snip-
>> I think the default is that it only shows new messages... But it
>> doesn't automatically show the old messages in that thread.
>
> Sorry, I got you wrong. See
>
> ,----[ 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.
> | 
> | You can customize this variable.
> `----
>
> So set it to t, if you want complete threads, or set it to 'some (that's
> what I do), to get as many old articles as are needed to build a
> complete sumthread.
>
> If it's set to nil (the default) no old headers will be fetched.
>
> So put either
>
>   (setq gnus-fetch-old-headers t) ;; complete threads
>
> or
>
>   (setq gnus-fetch-old-headers 'some) ;; complete subthreads
>
> into your ~/.gnus.el.

Thanks a lot - that was pretty clear and easy to understand.

I've now set it to "complete subthreads" and tried it a bit. It shows a
couple of old postings now, but not many... I might experiment a bit
with this, but it looks better now...


Best regards
Martin Jørgensen

-- 
---------------------------------------------------------------------------
Home of Martin Jørgensen - http://www.martinjoergensen.dk

  parent reply	other threads:[~2006-05-31  3:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 16:28 Martin Jørgensen
2006-05-23 16:57 ` David Z Maze
2006-05-24 23:05   ` Martin Jørgensen
2006-05-25  8:46     ` Alexander Ponomarenko
2006-05-25 15:03       ` Martin Jørgensen
2006-05-25 15:38         ` Malte Spiess
2006-05-25 23:06           ` Martin Jørgensen
2006-05-26  6:24             ` Malte Spiess
2006-05-26 15:20               ` Martin Jørgensen
2006-05-26 17:47                 ` Tassilo Horn
     [not found]                 ` <mailman.2324.1148665716.9609.info-gnus-english@gnu.org>
2006-05-26 18:29                   ` Karl Kleinpaste
2006-05-26 19:28                     ` Martin Jørgensen
2006-05-26 20:32                       ` Reiner Steib
2006-05-27  1:16                         ` Martin Jørgensen
2006-05-28  9:19                           ` Tassilo Horn
     [not found]                           ` <mailman.2366.1148808000.9609.info-gnus-english@gnu.org>
2006-05-28 15:22                             ` Martin Jørgensen
2006-05-28 16:16                               ` Tassilo Horn
2006-05-28 16:38                               ` Reiner Steib
2006-05-28 17:05                                 ` David Kastrup
2006-05-30 14:01                                   ` Reiner Steib
2006-05-30 15:33                                     ` David Kastrup
2006-05-31 22:35                                   ` Martin Jørgensen
2006-06-01  8:02                                     ` David Kastrup
2006-06-05 13:15                                     ` david.reitter
2006-06-15 13:55                                       ` Aking TIAN
2006-05-29  9:23                               ` Reiner Steib
     [not found]                               ` <mailman.2368.1148833009.9609.info-gnus-english@gnu.org>
2006-05-29 18:13                                 ` Martin Jørgensen
2006-05-29 22:22                                   ` Reiner Steib
2006-05-31  2:18                                     ` Martin Jørgensen
2006-05-31  8:13                                       ` Reiner Steib
2006-05-31 22:56                                         ` Martin Jørgensen
2006-05-30 17:45                                   ` Tassilo Horn
     [not found]                                   ` <mailman.2439.1149011220.9609.info-gnus-english@gnu.org>
2006-05-31  3:10                                     ` Martin Jørgensen [this message]
2006-05-23 22:02 ` Johan Bockgård
2006-05-24 23:08   ` Martin Jørgensen
2006-05-24 11:12 ` Alexander Ponomarenko

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=13evk3-qk6.ln1@news.tdc.dk \
    --to=unoder.spam@spam.jay.net \
    /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).