From: Istvan Marko <notmuch@kismala.com>
To: notmuch@notmuchmail.org
Subject: Re: Reply all - issue
Date: Wed, 06 Feb 2013 10:19:50 -0800 [thread overview]
Message-ID: <m3d2wd2tkp.fsf@zsu.kismala.com> (raw)
In-Reply-To: <CA+pa1O3zdpz+43eJpsJwakV72_Fr5U4Dvk1ta1su7M701bx9mw@mail.gmail.com> ("Michał Nazarewicz"'s message of "Mon, 4 Feb 2013 11:39:44 +0100")
Michał Nazarewicz <mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
writes:
> I was actually wondering that instead of hard coding the logic into notmuch
> itself, maybe it would be better to provide some sort of "split-thread" and
> "join-threads" which could than be used by separate tagging tool.
Such a customized threading feature would be great, I would use it to
tie together "loose threads" originating from crappy ticket tracking
tools that don't insert any In-Reply-To or References headers. Currently
I handle this by inserting fake In-Reply-To headers during delivery and
I would love to have a cleaner way.
To make this useful it would have to be persistent across dumps and
restores.
If we only consider splitting then a relatively easy way might be to
allow the user to configure some tags to mark a split. In
.notmuch-config you'd have:
split_tags: split
And then you'd tag +split the message to mark the start of a new
thread. The threading code would watch for such tags. Which might get
hairy if the tag information is not already at hand during threading.
I don't see how this would work for joins so it would not help me but it
could address the original problem.
--
Istvan
prev parent reply other threads:[~2013-02-06 18:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 21:58 Reply all - issue Robert Mast
2013-01-28 15:13 ` Jani Nikula
2013-01-28 18:15 ` Robert Mast
2013-01-29 2:47 ` Carl Worth
2013-01-30 17:14 ` Robert Mast
2013-01-30 21:39 ` Suvayu Ali
2013-01-31 10:21 ` Andrei POPESCU
2013-01-30 20:56 ` Robert Mast
2013-01-30 21:49 ` Robert Mast
2013-01-31 1:12 ` David Bremner
2013-01-31 1:14 ` David Bremner
2013-02-12 7:07 ` Jameson Graef Rollins
2013-02-12 19:17 ` Carl Worth
2013-01-31 10:52 ` Michał Nazarewicz
2013-02-02 16:21 ` Robert Mast
2013-02-02 20:52 ` David Bremner
2013-02-03 0:06 ` [Spam-verdenking][english 100%] " Robert Mast
2013-02-03 15:26 ` Robert Mast
2013-02-03 18:28 ` David Bremner
2013-02-10 15:43 ` Robert Mast
2013-02-04 10:39 ` Michał Nazarewicz
2013-02-04 15:29 ` Suvayu Ali
2013-02-06 18:19 ` Istvan Marko [this message]
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=m3d2wd2tkp.fsf@zsu.kismala.com \
--to=notmuch@kismala.com \
--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).