unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Summary by thread in rmail
Date: Thu, 6 Oct 2022 09:29:19 +0200	[thread overview]
Message-ID: <Yz6Dz67C8KdSBTip@tuxteam.de> (raw)
In-Reply-To: <87lept76z0.fsf@autistici.org>

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

On Thu, Oct 06, 2022 at 09:21:23AM +0200, Andrea Monaco wrote:
> 
>   > Great, but you are aware of Emacs Gnus?
> 
> Yes, but I prefer rmail, because I find the interface clearer.
> 
> 
>   > IOW, what is the use case for this new command that the existing
>   > C-M-t doesn't support?
> 
> That seems obvious to me.  C-M-t only shows a single thread, while my
> patch shows all mail this way.  This is useful to me, and is a common
> feature among mail clients.  I think Gnome Evolution shows mail by
> thread by default.

Still a pity that it guesses its threads by Subject: instead of using
In-Reply-To: and References:

In this way not better than the Microsoft "products" :-(

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-10-06  7:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 21:57 [PATCH] Summary by thread in rmail Andrea Monaco
2022-10-06  6:02 ` Eli Zaretskii
2022-10-06  7:21   ` Andrea Monaco
2022-10-06  7:29     ` tomas [this message]
2022-10-06 19:19       ` Emanuel Berg
2022-10-06 10:20     ` Eli Zaretskii
2022-10-06 10:55       ` Andrea Monaco
2022-10-06 14:18         ` Eli Zaretskii
2022-10-06 19:23         ` Emanuel Berg
2022-10-06 19:25         ` Emanuel Berg
2022-10-10  7:15 ` Eli Zaretskii
2022-11-15 19:07   ` [PATCH] Add command rmail-summary-by-thread (was: Summary by thread in rmail) Andrea Monaco
2022-11-17  4:34     ` Richard Stallman
2022-11-17 13:54     ` Eli Zaretskii
2022-12-09 20:22       ` [PATCH] Make rmail-summary-by-thread faster Andrea Monaco
2022-12-18 10:25         ` 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=Yz6Dz67C8KdSBTip@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.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.
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).