From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/5004 Path: main.gmane.org!not-for-mail From: Jason L Tibbitts III Newsgroups: gmane.emacs.gnus.general Subject: Can the tree show the _whole_ thread? Date: 31 Jan 1996 21:42:36 -0600 Organization: Blob Shop Programmers Sender: tibbs@hpc.uh.edu Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035145668 31483 80.91.224.250 (20 Oct 2002 20:27:48 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:27:48 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miranova.com (8.7.3/8.6.9) with SMTP id UAA25313 for ; Wed, 31 Jan 1996 20:15:59 -0800 Original-Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Thu, 1 Feb 1996 04:42:59 +0100 Original-Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id VAA20690; Wed, 31 Jan 1996 21:42:58 -0600 (CST) Original-To: ding@ifi.uio.no Original-Lines: 42 Xref: main.gmane.org gmane.emacs.gnus.general:5004 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:5004 My belief is that the summary buffer should show a good bit of info about the articles of interest, the tree buffer shows the big picture with less detail, and the article buffer shows everything about just one message. So I sort of expected the tree display to show the entire thread, including old articles and sparse nodes and everything. I tried playing with gnus-fetch-old-headers and gnus-make-sparse-threads and can get old and sparse articles to show up in the summary buffer but the tree buffer shows only the new articles and whatever sparse nodes are required to connect them (as it always does). What I'm really trying to get is a summary buffer with no extraneous information (no O or Q lines) but a tree buffer with a picture of everything back to the root article, preferably with old articles shown like sparse articles, but with useful info instead of ***. For example, I get this: I want this: {***} (***) |--\-----\ |--\-----\ [Ste] [Mar] [Per] (Bla) (***) (Ste) | | | (Mar) (Urk) [Per] | | (Joe) [Ste] | [Mar] And a summary buffer that just looks like: +[ 106: Steven L. Baur ] Re: Gnus5, procmail, and reading mail + < 82: Mark Borges > + < 24: Per Abrahamsen > I.e. I can see the whole conversation, but some of the articles are old (like "(Bla)" and "(Urk)") or have expired (like the root) and the summary buffer is really simple. Is this possible? Somehow I think it's not, given that both buffers work from the same information and the summary buffer always displays everything in the list of threads. Perhaps for Red Gnus? - J<