From: Matt Armstrong <marmstrong@google.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Gaute Hope <eg@gaute.vetsj.com>,
David Bremner <david@tethera.net>,
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: Mon, 26 Jun 2017 13:54:08 -0700 [thread overview]
Message-ID: <qf5zicutqq7.fsf@google.com> (raw)
In-Reply-To: <87efu8t6ia.fsf@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> Hey all--
>
> I really appreciate the thought and experimentation and research that's
> gone into this thread!
>
> On Thu 2017-06-22 17:00:58 -0700, Matt Armstrong wrote:
>> # All threads in which I participate get tag:participated
>> # 1) Find all threads with a message tagged new
>> # (finding all 'today' messages helps during testing,
>> # but isn't necessary)
>> # 2) Run through "xargs -s 2048 echo" to to group threads
>> # lines of about 2K in size.
>> # 3) For each line (2) produces, narrow the threads to
>> # those containing a message from me.
>> # 4) For each such thread, tag every message with +participated.
>> notmuch search --output=threads tag:new OR date:today | \
>> xargs -s 2048 echo | \
>> xargs -I '{}' notmuch search \
>> --output=threads from:marmstrong AND \( '{}' \) | \
>> sed -e 's,^,+participated -- ,' | \
>> notmuch tag --batch
>
> This makes sense to me, modulo the split into 2048-octet lines (magic
> numbers make me nervous, though i think i understand why you've included
> it).
Yes, the two xargs commands and "2048 business" is just a hack to work
around the documented limitations of "xargs -I". I'd love to come up
with a simpler way to do this. I suspect there is one, but when it
comes to this kind of Unix shell hackery, I usually stop once I get to
something that works. :)
next prev parent reply other threads:[~2017-06-26 20:54 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
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 [this message]
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=qf5zicutqq7.fsf@google.com \
--to=marmstrong@google.com \
--cc=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=eg@gaute.vetsj.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).