From: Jani Nikula <jani@nikula.org>
To: Matt Armstrong <marmstrong@google.com>,
David Bremner <david@tethera.net>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Gaute Hope <eg@gaute.vetsj.com>,
notmuch@notmuchmail.org, Xu Wang <xuwang762@gmail.com>
Subject: Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Date: Sun, 20 Aug 2017 16:35:26 +0300 [thread overview]
Message-ID: <8760dil5up.fsf@nikula.org> (raw)
In-Reply-To: <qf537amv5ht.fsf@google.com>
On Mon, 26 Jun 2017, Matt Armstrong <marmstrong@google.com> wrote:
> David Bremner <david@tethera.net> writes:
>
>> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>>
>>>
>>> For example, would it make sense to have "notmuch new" (and "notmuch
>>> insert") do "thread-based propagation" of specific tags? for example,
>>> consider the following (i've just made up the config options):
>>>
>>> notmuch config set new.from_self_tags participated
>>> notmuch config set new.propagate_thread_tags participated
>>>
>>> the idea is that "new.from_self_tags" would be applied by "notmuch new" or
>>> "notmuch insert" if the message was explicitly from: user.primary_email
>>> or user.other_email.
>>
>> At the moment I'm more inclined to work on "doing things right" by
>> adding xapian documents (database items) for threads. Many of the
>> ideas in this thread amount to working around their absence. OTOH,
>> it's certainly true that this last idea (unlike some of the query
>> ideas) would be relatively straightforward to impliment.
>
> David, that makes a lot of sense.
>
> Take two other examples from my post-hook:
>
> # Unmute all threads with new messages sent to me.
> notmuch search --output=threads tag:new AND tag:me | \
> xargs --no-run-if-empty notmuch tag -muted --
>
> # Remove all muted threads from the inbox and mark
> # every message in them muted.
> notmuch search --output=threads tag:muted | \
> xargs --no-run-if-empty notmuch tag -inbox +muted --
>
> Above I'm just operating on all the messages in a thread as a unit. If
> notmuch had a 'database item' for each thread, I could potentially tag
> just that to achieve similar results with simpler commands.
FWIW, this is my approach to "thread tags", from my post-new hook:
# Propagate thread tags
THREAD_TAGS="muted"
for tag in $THREAD_TAGS; do
notmuch tag +$tag $(notmuch search --output=threads tag:$tag)
done
Basically if I tag a message muted, all messages in the thread will get
the tag on next post-new.
This may or may not be related to the problems people in this thread are
trying to solve. ;)
BR,
Jani.
next prev parent reply other threads:[~2017-08-20 13:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 21:55 find threads where I and Jian participated but not Dave Xu Wang
2017-06-13 15:57 ` Xu Wang
2017-06-13 23:31 ` David Bremner
2017-06-14 0:24 ` Xu Wang
2017-06-14 3:32 ` Brian Sniffen
2017-06-15 17:54 ` Daniel Kahn Gillmor
2017-06-15 20:20 ` David Bremner
2017-06-16 1:07 ` Matt Armstrong
2017-06-16 6:28 ` Gaute Hope
2017-06-21 20:04 ` Matt Armstrong
2017-06-21 21:30 ` Daniel Kahn Gillmor
2017-06-22 6:08 ` Gaute Hope
2017-06-22 6:22 ` Gaute Hope
2017-06-23 0:00 ` Matt Armstrong
2017-06-25 15:46 ` finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave] Daniel Kahn Gillmor
2017-06-25 17:14 ` David Bremner
2017-06-26 20:49 ` Matt Armstrong
2017-06-26 23:09 ` David Bremner
2017-08-20 13:35 ` Jani Nikula [this message]
2017-08-20 13:48 ` Jani Nikula
2017-08-20 21:32 ` [PATCH] WIP: add thread subqueries David Bremner
2017-08-21 1:35 ` David Bremner
2017-09-07 17:47 ` Gaute Hope
2017-09-07 18:51 ` David Bremner
2017-06-25 17:40 ` finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave] Brian Sniffen
2017-06-26 20:54 ` Matt Armstrong
2017-06-22 20:15 ` find threads where I and Jian participated but not Dave Matt Armstrong
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=8760dil5up.fsf@nikula.org \
--to=jani@nikula.org \
--cc=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=eg@gaute.vetsj.com \
--cc=marmstrong@google.com \
--cc=notmuch@notmuchmail.org \
--cc=xuwang762@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 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).