From: Eli Zaretskii <eliz@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: andrea.monaco@autistici.org, emacs-devel@gnu.org, rameiko87@posteo.net
Subject: Re: Rmail: new feature to deal with In-Reply-To and References headers
Date: Wed, 13 Dec 2023 15:34:31 +0200 [thread overview]
Message-ID: <83il52rztk.fsf@gnu.org> (raw)
In-Reply-To: <87a5qe1btj.fsf@tucano.isti.cnr.it> (message from Francesco Potortì on Wed, 13 Dec 2023 14:17:28 +0100)
> From: Francesco Potortì <pot@gnu.org>
> Date: Wed, 13 Dec 2023 14:17:28 +0100
> Cc: emacs-devel@gnu.org,
> eliz@gnu.org,
> rameiko87@posteo.net
>
> Andrea Monaco:
> >I don't fully understand your needs, or maybe we use slightly different
> >definitions of a thread. In my implementation, belonging to the same
> >thread is an equivalence relation: no matter which message of the thread
> >you start from, you always end up with the same thread; ie there's no
> >notion of "centering" on a given message.
> >
> >About ordering: a thread is represented as a boolean vector indexed by
> >message index, so the messages in a thread summary have the same
> >ordering, ie by the first field of the summary line (which mirrors the
> >ordering in the RMAIL file, I think).
>
> Well, the ordering in fact is more complex as in general there is no total order. Unless I am missing something, a thread can be partially ordered, and can be represented by a directed acyclic graph, but not generally by a linear array.
What Andrea says, AFAIU, is that the order is according to the summary
from which you invoked rmail-summary-by-thread. Since the "usual"
summary is in the order of receiving the messages, that is what you
get; it is usually the actual order of responses to older messages,
unless there was some interruption in email delivery, in which case in
many cases the order could be the reverse: LIFO.
So one could first invoke rmail-sort-by-date, and after that
rmail-summary-by-thread, and get the thread messages in strict
chronological order, which should be close to the requested ordering,
no (the DAG thing aside)?
prev parent reply other threads:[~2023-12-13 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 15:35 Rmail: new feature to deal with In-Reply-To and References headers rameiko87
2023-12-09 15:49 ` Eli Zaretskii
2023-12-09 21:54 ` rameiko87
2023-12-10 5:48 ` Eli Zaretskii
2023-12-13 10:27 ` Andrea Monaco
2023-12-13 13:17 ` Francesco Potortì
2023-12-13 13:34 ` Eli Zaretskii [this message]
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=83il52rztk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrea.monaco@autistici.org \
--cc=emacs-devel@gnu.org \
--cc=pot@gnu.org \
--cc=rameiko87@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.