From: Eric <eric@deptj.eu>
To: notmuch@notmuchmail.org
Subject: Re: Breaking a really long thread
Date: Mon, 04 Apr 2016 13:07:45 +0200 (CEST) [thread overview]
Message-ID: <c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu> (raw)
In-Reply-To: <874mbkyv0j.fsf@ta.scs.stanford.edu>
On Sat, 02 Apr 2016 06:56:12 -0700, David Mazieres <dm-list-email-notmuch@scs.stanford.edu> wrote:
> David Bremner <david@tethera.net> writes:
>
>> David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:
>>
>>> Is there any way to break an existing thread (so as to start over with a
>>> smaller thread), or otherwise to tweak the threading rules so that a
>>> particular References header gets ignored.
>>
>> Currently there is no way to do this, as threads are "stateless"
>> i.e. created on the fly by _notmuch_create_thread based only on
>> immutable mail data.
>
> Thanks.
>
>>> It's annoyingly slow to open
>>> a thread with 10,000 messages just to read one SMS. I'm almost tempted
>>> to mangle the messages on delivery and remove the References header
>>> before notmuch sees them, but it would be nice to have a cleaner
>>> solution, as there are other situations in which one might want to
>>> "reset" a really long thread.
>>
>> Like this thread ;).
>
> Oops, sorry for the irrelevant thread inclusion. I guess emacs adds the
> References header after a message is sent is sent? In my setup, the
> easiest way to post to a mailing list is to reply to an existing message
> (since I subscribe to each list under a different email address). I
> tried to start a new thread by deleting the In-Reply-To and header which
> was all I saw, but I guess the References header got inserted later...
Neither notmuch emacs nor any other email client has any business
inserting a References header after the user "presses Send". On a new
message it shouldn't exist unless inserted manually, and on a reply it
should come from the replied-to message (and be changed) before you start
"replying". More likely that (if you didn't miss it) it was not shown
to you although it existed - that would count as a bug in my opinion
(I don't use emacs for anything, not even notmuch).
Actually the message you replied to has no References header, but notmuch
reply (command line) to it generates both References and In-Reply-To
(same content). I assume notmuch emacs does the same. I don't believe
that References should be generated in this situation, its only use
would be by a threading algorithm that doesn't use In-Reply-To, and I
would consider that a bug in said algorithm.
Actually I think there should be a "reply as new" option which uses
the other message but does not add either In-Reply-To or References
(and does not carry the latter forward if it exists).
Eric
--
ms fnd in a lbry
next prev parent reply other threads:[~2016-04-04 11:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 17:57 v2 of libconfig, date:foo, and named query patches David Bremner
2016-03-26 17:57 ` [Patch v2 01/13] configure: autodetect xapian-1.3 David Bremner
2016-04-01 9:09 ` Tomi Ollila
2016-04-01 23:29 ` David Bremner
2016-03-26 17:57 ` [Patch v2 02/13] configure: detect Xapian:FieldProcessor David Bremner
2016-03-26 17:57 ` [Patch v2 03/13] lib: optionally support single argument date: queries David Bremner
2016-03-26 17:57 ` [Patch v2 04/13] lib/cli: add library API / CLI for compile time options David Bremner
2016-04-27 17:47 ` Tomi Ollila
2016-04-30 11:53 ` David Bremner
2016-05-01 17:48 ` Tomi Ollila
2016-03-26 17:57 ` [Patch v2 05/13] configure: check directly for xapian compaction API David Bremner
2016-03-26 17:57 ` [Patch v2 06/13] lib: provide config API David Bremner
2016-03-26 17:57 ` [Patch v2 07/13] lib: config list iterators David Bremner
2016-03-26 17:57 ` [Patch v2 08/13] CLI: add print_status_database David Bremner
2016-03-27 20:25 ` [PATCH] nmbug: ignore # comments David Bremner
2016-03-27 20:38 ` W. Trevor King
2016-03-28 7:14 ` Tomi Ollila
2016-03-28 12:33 ` David Bremner
2016-03-26 17:57 ` [Patch v2 09/13] CLI: add optional config data to dump output David Bremner
2016-03-26 18:13 ` David Bremner
2016-03-26 17:57 ` [Patch v2 10/13] CLI: optionally restore config data David Bremner
2016-03-26 17:57 ` [Patch v2 11/13] CLI: add notmuch-config support for named queries David Bremner
2016-03-26 17:57 ` [Patch v2 12/13] lib: make a global constant for query parser flags David Bremner
2016-03-26 17:57 ` [Patch v2 13/13] lib: add support for named queries David Bremner
2016-04-01 23:57 ` Breaking a really long thread David Mazieres
2016-04-02 12:41 ` David Bremner
2016-04-02 13:56 ` David Mazieres
2016-04-04 11:07 ` Eric [this message]
2016-04-04 13:00 ` Mark Walters
2016-04-04 15:38 ` Eric
2016-04-05 5:28 ` David Mazieres
2016-04-09 11:20 ` Daniel Kahn Gillmor
2016-04-09 18:55 ` David Bremner
2016-04-09 22:40 ` Mark Walters
2016-04-11 2:05 ` David Bremner
2016-04-11 7:19 ` Mark Walters
2016-04-11 7:39 ` David Edmondson
2016-04-11 9:57 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu \
--to=eric@deptj.eu \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).