all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 83587bb 1/2: Correctly cache sorted completions in icomplete--sorted-completions
Date: Thu, 26 Dec 2019 22:33:14 +0200	[thread overview]
Message-ID: <834kxmrfn9.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm50Ua-KqXGbPWeQndXB6Nk_rWh1KWR3s8VpgkN-_vTT7jQ@mail.gmail.com> (message from João Távora on Thu, 26 Dec 2019 17:31:25 +0000)

> From: João Távora <joaotavora@gmail.com>
> Date: Thu, 26 Dec 2019 17:31:25 +0000
> 
> >   https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00635.html
> >
> > and it definitely starts a new thread.
> 
> That's the one I had in mind. It appears in the longer-running "Starting the
> Emacs 27 release cycle" thread as a reply to Bastien's
> https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00129.html
> (as you can see by following the link your posted).

That's the mailman archiving feature being too "smart".  I didn't
remove any Re from the subject, I wrote an entirely new message.  It
just happened to use the same Subject line as some previous
discussion, so mailman decided they were the same thread.  If you
examine the mail headers of my message, you will see that it doesn't
have the other messages in its References header, and no In Reply To,
either.  I hope the MUA you are using to read the mailing list is
smarter than mailman.

> Even though you removed the "Re:" from the subject, Gmail also hides it in the
> same "conversation", so it doesn't stand out as a new thread.

So you may wish to submit a bug report against Gmail for too naïve
threading.

> Maybe I should blame Gmail. I'm working on ditching it, or at least
> the web client,
> but can't seem to close the deal :-(

Using any MUA we have in Emacs will produce much better results.



  parent reply	other threads:[~2019-12-26 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191225175851.21930.86980@vcs0.savannah.gnu.org>
     [not found] ` <20191225175852.DE63E20997@vcs0.savannah.gnu.org>
2019-12-26 11:39   ` master 83587bb 1/2: Correctly cache sorted completions in icomplete--sorted-completions Dmitry Gutov
2019-12-26 11:48     ` João Távora
2019-12-26 17:20       ` Eli Zaretskii
2019-12-26 17:48         ` João Távora
     [not found]         ` <CALDnm50Ua-KqXGbPWeQndXB6Nk_rWh1KWR3s8VpgkN-_vTT7jQ@mail.gmail.com>
2019-12-26 20:33           ` Eli Zaretskii [this message]
2019-12-26 20:42             ` João Távora
2019-12-26 22:25               ` Juanma Barranquero
2019-12-27  8:31                 ` João Távora
2019-12-27  8:39                   ` Mario Lang
2019-12-27  9:17                   ` Eli Zaretskii
2019-12-27  9:26                     ` João Távora
2019-12-27  2:24             ` Stefan Monnier
2019-12-26 17:22       ` Eli Zaretskii
2019-12-26 17:22         ` João Távora

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=834kxmrfn9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    /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.