From: Jack Twilley <jmt+usenet@nycap.rr.com>
Subject: Email folders and threading
Date: 13 Nov 1999 19:04:09 -0500 [thread overview]
Message-ID: <m39042ym4m.fsf@duchess.twilley.org> (raw)
I've noticed something frustrating about extended email conversations.
This is what the summary buffer looks like for
nnml:people.Charlotte_Evans:
OA [ 40: +Charlotte Evans ] conversation
Q [ 0: ]
OA [ 27: +Charlotte Evans ]
Here's what the References: header looks like in the second message:
References: <01e001bf1a7a$09ab3250$2280d0d1@evolution.com> <m3wvsjowcq.fsf@duchess.twilley.org>
So the second message knows that there's a message between it and the
first message -- namely, my reply to the first message, which is
sitting in nnfolder+archive:mail.1999-10.
WIBNI the summary buffer for nnml:people.Charlotte_Evans looked like
this:
OA [ 40: +Charlotte Evans ] conversation
Q [ 48: +Jack Twilley ]
OA [ 27: +Charlotte Evans ]
And that the summary buffer for nnfolder+archive:mail.1999-10 looked
like this:
O [ 48: +Jack Twilley ] Re: conversation
Q [ 27: +Charlotte Evans ]
O + [ 57: +Jack Twilley ]
Or maybe even like this:
OA [ 40: +Charlotte Evans ] conversation
Q [ 48: +Jack Twilley ]
OA [ 27: +Charlotte Evans ]
O + [ 57: +Jack Twilley ]
After all, the last message has all the references.
This might require the creation of some big hash of message-id's, such
that $hash{message-id} = "protocol+server:folder[articleno]" or
something to that effect.
Thoughts?
Jack.
(I'm better at perl than elisp.)
--
Jack Twilley
jmt at nycap dot rr dot com
http colon slash slash jmt dot dhs dot org slash tilde jmt slash
next reply other threads:[~1999-11-14 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-14 0:04 Jack Twilley [this message]
1999-11-14 10:39 ` Kai Großjohann
1999-11-14 14:24 ` Jack Twilley
1999-11-15 19:42 ` Lars Magne Ingebrigtsen
1999-11-16 9:07 ` Kai Großjohann
1999-12-01 14:39 ` Lars Magne Ingebrigtsen
1999-12-01 19:28 ` Kai Großjohann
1999-12-02 11:56 ` Toby Speight
1999-12-02 16:56 ` Simon Josefsson
1999-12-05 22:06 ` Kai Großjohann
1999-12-06 3:38 ` Lars Magne Ingebrigtsen
1999-12-06 13:10 ` Kai Großjohann
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=m39042ym4m.fsf@duchess.twilley.org \
--to=jmt+usenet@nycap.rr.com \
/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).