From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: hack of .overview files [take 2]
Date: 04 Mar 1998 12:16:40 +0100 [thread overview]
Message-ID: <rjd8g2iu3r.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: <utt67lvk0qp.fsf@gs236.sp.cs.cmu.edu>
Mark Moll <mmoll@cs.cmu.edu> writes:
> Okay, here's my second try. This time it looks (hopefully) somewhat less
> like a hack, but more like a real feature.
It still unnecessarily breaks the NOV format.
The right way would be to add an extra field to the end of each line
in the .overview file, like this:
[...] Xref: blah blah blah To: ding@gnus.org
and then add a new escape to `gnus-summary-line-format' with semantics
like
%X Name of the poster unless it matches
`gnus-uninteresting-senders', content of the From:
header otherwise.
Personally, I split in and outgoing mail into the same folders, so my
email conversations are in one place, nicely threaded.
next prev parent reply other threads:[~1998-03-04 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-03 15:59 hack of .overview files Mark Moll
1998-03-03 16:04 ` Stefan Waldherr
1998-03-03 16:42 ` Wes Hardaker
1998-03-03 17:37 ` Per Abrahamsen
1998-03-03 19:55 ` hack of .overview files [take 2] Mark Moll
1998-03-04 11:16 ` Per Abrahamsen [this message]
1998-03-05 11:20 ` threading emails (Was: hack of .overview...) Steinar Bang
1998-03-05 13:07 ` Per Abrahamsen
1998-03-07 12:59 ` hack of .overview files [take 2] 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=rjd8g2iu3r.fsf@zuse.+dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).