Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: How to show all messages in threads where unread exist
Date: Wed, 5 Nov 2014 19:37:44 +0000	[thread overview]
Message-ID: <87lhnpsak7.fsf@ucl.ac.uk> (raw)
In-Reply-To: <m2389xk1rz.fsf@gmail.com> (Andrey Lisin's message of "Wed, 5 Nov 2014 23:14:40 +0600")

On Wednesday,  5 Nov 2014 at 23:14, Andrey Lisin wrote:
> Hello,
>
> Probably it's silly question, but I didn't find the answer in the Gnus
> documentation. How to show all messages in threads, where unread
> messages exist?

I don't think it's easy to show all messages in threads but you can
easily show all those that are direct predecessors in the thread.

"A T" at the summary may do what you want or part thereof.

You might also wish to look at

,----[ C-h v gnus-fetch-old-headers RET ]
| gnus-fetch-old-headers is a variable defined in `gnus-sum.el'.
| Its value is t
| Original value was nil
| 
| 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.
| 
| You can customize this variable.
| 
| [back]
`----

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-999ec15
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)



           reply	other threads:[~2014-11-05 19:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m2389xk1rz.fsf@gmail.com>]

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=87lhnpsak7.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ding@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).