unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rameiko87@posteo.net, Andrea Monaco <andrea.monaco@autistici.org>
Cc: emacs-devel@gnu.org
Subject: Re: Rmail: new feature to deal with In-Reply-To and References headers
Date: Sun, 10 Dec 2023 07:48:02 +0200	[thread overview]
Message-ID: <83il56wqul.fsf@gnu.org> (raw)
In-Reply-To: <329adea46dd0abf07b03369a0fbe97d0@posteo.net> (rameiko87@posteo.net)

> Date: Sat, 09 Dec 2023 21:54:36 +0000
> From: rameiko87@posteo.net
> Cc: emacs-devel@gnu.org
> 
> > AFAIU, you should already be able to do that in Emacs 29, by using the 
> > new command rmail-summary-by-thread.  After creating that summary, you 
> > can use the usual message movement commands to move between messages 
> > belonging to a thread.
> 
> In fact it's not the case, because the order on the summary buffer 
> centered on a given message does not correspond in general to the 
> parents-descendants order of the thread containing that given message, 
> as defined by moving up on the References header for that message.
> 
> >> Move to the previous message in the same thread as the current one 
> >> (that is, the message whose Message-ID is the last entry of the 
> >> References header, among messages in the Rmail file). Repeat argument 
> >> goes back to the n-th last entry of the References header among 
> >> messages in the Rmail file.
> 
> This feature is not implemented currently unless the parents vector is 
> populated with the same order given by the References header. Someone 
> remembers how the parents vector is recursively defined in rmailsum.el?
> 
> And still, going up on the chain requires regenerating the summary 
> buffer by centering every time on the parent.
> 
> >> Move to the message which the current message is replying to (that is, 
> >> the message whose Message-ID appears in the In-Reply-To header), error 
> >> if not present on the Rmail file. Repeat argument iterates the command 
> >> n-times, perhaps replacing the messages which it can't find in the 
> >> Rmail file by their youngest parent.
> 
> This is not implemented currently.

Patches to improve the existing implementation of by-thread summary
will be welcome, of course.  It is a new feature, so I'm not surprised
that it has some rough edges.

Adding Andrea, who implemented this feature, in the hope that he will
have some comments or maybe patches.



  reply	other threads:[~2023-12-10  5:48 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 [this message]
2023-12-13 10:27     ` Andrea Monaco
2023-12-13 13:17       ` Francesco Potortì
2023-12-13 13:34         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83il56wqul.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrea.monaco@autistici.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).