From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Email folders and threading
Date: 15 Nov 1999 20:42:52 +0100 [thread overview]
Message-ID: <m34senr16r.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m39042ym4m.fsf@duchess.twilley.org>
Jack Twilley <jmt+usenet@nycap.rr.com> writes:
> 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?
You could stuff that hash-adding function down into
`message-sent-hook'. And for display, you could just do a
user-defined format spec. Shouldn't be too complicated to do.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-11-15 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-14 0:04 Jack Twilley
1999-11-14 10:39 ` Kai Großjohann
1999-11-14 14:24 ` Jack Twilley
1999-11-15 19:42 ` Lars Magne Ingebrigtsen [this message]
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=m34senr16r.fsf@quimbies.gnus.org \
--to=larsi@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).