From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Sparse threads
Date: 20 Jan 1996 06:25:06 +0100 [thread overview]
Message-ID: <w8szqbjmo99.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: gsstark@MIT.EDU's message of 19 Jan 1996 08:15:22 -0500
gsstark@MIT.EDU (Greg Stark) writes:
> i am now looking at article 3:
> [1] - [2]
> \ - [3]
> i believe with a setting of t (equivalent of 'some) it will show me [1] but
> not [2], the old reply. in other words, sparse threads will get me:
> [1] - [3]
> i think it is relatively important to know that i've already seen a reply.
September 0.30 allows a `more' value to `gnus-build-sparse-threads'
that won't cut off these leaf nodes.
> the other scenario is in my mail groups. a lot of the mail in my
> mail box consists of replies to mail i sent out. the mail i sent
> out isn't in my mail box of course, but it is (now) stored in the
> mail archive. it would be nice if gnus would check for any missing
> article msg-id's in the outgoing mail (and maybe news) archive.
> This would actually make sparse threads useful in mail groups;
> currently all it does is make a lot of pieces of mail take two
> lines, one of which is mostly content-free.
Uhm. I don't think Gnus should go check the archive group; that would
take too long. However, you will be able to select these sparse nodes
in the future, and that selection is done on Message-ID. So you could
just set `gnus-refer-article-method' to the archive server in you mail
groups, and *presto*. This'll fill out the line in the summary buffer
with the proper information, even.
--
Home is where the cat is.
next prev parent reply other threads:[~1996-01-20 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-08 12:08 Lars Magne Ingebrigtsen
1996-01-10 18:41 ` Per Abrahamsen
1996-01-11 21:25 ` Lars Magne Ingebrigtsen
1996-01-19 13:15 ` Greg Stark
1996-01-20 5:25 ` Lars Magne Ingebrigtsen [this message]
1996-01-20 14:09 ` Greg Stark
1996-01-20 22:07 ` d. hall
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
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=w8szqbjmo99.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).