Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: Showing Complete Active Threads
Date: Wed, 08 Mar 2006 20:43:41 +0100	[thread overview]
Message-ID: <87acc0bu36.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: <lzek1cvkca.fsf@null.nullsome.net>

Rolleston <Nemo@nullsome.net> writes:

> Somewhat suboptimal, I'd say, as it seems to often try to receive
> every available header.

Sorry, I cannot follow you here. What do you mean with that it often
tries to receive every available header?

> I instruct gnus to fetch old headers:
>
>   M-: (setq gnus-fetch-old-headers 1000)
>
> [snip]
>
> So far so good :) Now I check for new messages (perhaps not necessaray
> to do that) and hit <RET> to reenter the summar buffer. And this is
> what I see:
>
>     08 Mar 08:38 Re: Showing Complete Active Threads Tassilo Horn

Hm, ok. Here I would expect the parent (your opening question), too.

> Oh... it's a loose thread. What happens if I type A R? Let's see now:
>
>   R 08 Mar 06:07 Showing Complete Active Threads Rolleston
>     08 Mar 08:38 \->  Tassilo Horn
>
> And there it is, the whole thread. Hmm.. Ok. Let's try your suggestion
> (without the quote):
   ^^^^^^^^^^^^^^^^^

Sure. ;-)

>   M-u
>   M-: (setq gnus-fetch-old-headers t)
>
> We leap out of the summary buffer, and dive back in again:
>
>   O 08 Mar 06:07 Showing Complete Active Threads Rolleston
>     08 Mar 08:38 \->  Tassilo Horn
>
> Hmmph! What's going on here?

Isn't that the behaviour you were looking for?

BTW: I use

     (setq gnus-fetch-old-headers 'some)

which fetches only those old headers needed to prevent loose threads
(all old headers till a common parent article is found). That's more
concise and expresses this thread's structure as well.

Regards,
Tassilo

  reply	other threads:[~2006-03-08 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  6:07 Rolleston
2006-03-08  8:38 ` Tassilo Horn
2006-03-08 18:53   ` Rolleston
2006-03-08 19:43     ` Tassilo Horn [this message]
2006-03-08 20:50       ` Rolleston
2006-03-08 22:45         ` Tassilo Horn
2006-03-12 23:04           ` Rolleston
2006-03-09 11:31         ` Gnus fetches too many headers WAS: " Tassilo Horn
2006-05-14 15:43           ` Dale Worley
2006-05-14 18:33             ` Tassilo Horn
2006-05-15  7:07               ` Frank Schmitt
2006-05-15  7:48               ` Tassilo Horn
2006-03-15  0:48       ` Matt Ford
2006-03-15  1:08         ` Matt Ford

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=87acc0bu36.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).