help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-users@zsh.org
Subject: Re: key binding not working [SOLVED]
Date: Mon, 26 Sep 2022 21:43:03 +0200	[thread overview]
Message-ID: <CAHYJk3Qad_SCUMPhbtW9Ks6OzWRXVjHUZYpu_Zk__g5EjS7oBw@mail.gmail.com> (raw)
In-Reply-To: <679b74da59012dd0e0f3de84ff467235ba53f906.camel@ntlworld.com>

On 9/26/22, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> On Mon, 2022-09-26 at 20:13 +0200, Roman Perepelitsa wrote:
>> Your changing the subject broke threading. I think it's not a good idea
>> to do that.
> Actually, a poll of three local clients --- one desktop, one browser-based,
> one Android --- suggests it didn't universally break it, since they all
> handled it, so there is a bit of wiggle room here.  I would say it's an
> area
> where there isn't a definite right or wrong --- there are just too many
> different client behaviours to worry about to be too dogmatic.  Having
> said that, I tend to keep subject lines unaltered until the subject
> has actually changed --- and by the same token, you don't know even
> that's going to make your client use a new thread if it's going by
> message IDs.
> In summary, bleugh.
> pws
> P.S. Evolution, Vivaldi's internal client, and K9 Mail, in case you're
> wondering.

For all its virtues (probably countable on one hand), GMail still has
no support for threads after all these years. Trying to read lkml or
git is nigh impossible since all the PATCH x/50 threads are completely
disjointed. It simply groups mails naively by subject which is pretty
much objectively the wrong thing to do. (This also leads to a lot of
confusion when getting automated mails with the same subject line but
which aren't strictly related).

Mikael Magnusson

  reply	other threads:[~2022-09-26 19:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 21:14 key binding not working Ray Andrews
2022-09-25 22:31 ` Bart Schaefer
2022-09-25 22:46   ` Ray Andrews
2022-09-25 23:14     ` Ray Andrews
2022-09-26  3:48     ` Marc Chantreux
2022-09-27  0:30     ` zkbd (was Re: key binding not working) Bart Schaefer
2022-09-27  1:39       ` Ray Andrews
2022-09-26  1:16   ` key binding not working Ray Andrews
2022-09-26  1:58     ` Lawrence Velázquez
2022-09-26  3:15       ` Ray Andrews
2022-09-26  4:01         ` Lawrence Velázquez
2022-09-26  6:28     ` Roman Perepelitsa
2022-09-26 13:59       ` key binding not working [SOLVED] Ray Andrews
2022-09-26 18:04         ` Ray Andrews
2022-09-26 18:13           ` Roman Perepelitsa
2022-09-26 19:12             ` Peter Stephenson
2022-09-26 19:43               ` Mikael Magnusson [this message]
2022-09-26 21:31             ` Ray Andrews
2022-09-26 22:27               ` Vin Shelton
2022-09-26 22:35                 ` Ray Andrews

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:

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

  git send-email \
    --in-reply-to=CAHYJk3Qad_SCUMPhbtW9Ks6OzWRXVjHUZYpu_Zk__g5EjS7oBw@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=zsh-users@zsh.org \


* 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


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).