From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id CA0166DE173F for ; Sun, 25 Jun 2017 12:49:08 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.011 X-Spam-Level: X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bW1eqZ41wBTx for ; Sun, 25 Jun 2017 12:49:07 -0700 (PDT) Received: from istari.evenmere.org (istari.evenmere.org [136.248.125.194]) by arlo.cworth.org (Postfix) with ESMTP id 9DF056DE12BD for ; Sun, 25 Jun 2017 12:49:07 -0700 (PDT) Received: by istari.evenmere.org (Postfix, from userid 113) id 9572F1E0075; Sun, 25 Jun 2017 15:48:58 -0400 (EDT) Received: from [100.169.81.102] (unknown [172.56.7.7]) by istari.evenmere.org (Postfix) with ESMTPSA id 1AC311E005F; Sun, 25 Jun 2017 15:48:50 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Brian Sniffen Mime-Version: 1.0 (1.0) 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, 25 Jun 2017 13:40:20 -0400 Message-Id: <375694E6-017C-4D54-BE72-9C0376BDE5F4@evenmere.org> References: <87bmprtqgo.fsf@tethera.net> <87fuf1nnl5.fsf@fifthhorseman.net> <8737b1rojw.fsf@tethera.net> <1497594312.ahjx44w937.astroid@strange.none> <87r2ydgh9t.fsf@fifthhorseman.net> <1498111587.9x086zp6wn.astroid@strange.none> <1498112439.apimm1pnum.astroid@strange.none> <87efu8t6ia.fsf@fifthhorseman.net> Cc: Matt Armstrong , Gaute Hope , David Bremner , notmuch@notmuchmail.org, Xu Wang In-Reply-To: <87efu8t6ia.fsf@fifthhorseman.net> To: Daniel Kahn Gillmor X-Mailer: iPhone Mail (14F89) X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jun 2017 19:49:09 -0000 Well, it's not quite *away* from Turing complete configuration... but it sou= nds like you might like the program that computes tags for new messages to g= et not only the message but also its thread id and read-only access to the d= atabase? Then both filtering "participated" and computing "participated" fr= om "sent" become easy. And fancier ideas like computing tags from senders, l= ist-id, the rest.=20 --=20 Brian Sniffen > On Jun 25, 2017, at 11:46 AM, Daniel Kahn Gillmor w= rote: >=20 > Hey all-- >=20 > I really appreciate the thought and experimentation and research that's > gone into this thread! >=20 >> 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=3Dthreads tag:new OR date:today | \ >> xargs -s 2048 echo | \ >> xargs -I '{}' notmuch search \ >> --output=3Dthreads from:marmstrong AND \( '{}' \) | \ >> sed -e 's,^,+participated -- ,' | \ >> notmuch tag --batch >=20 > 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). >=20 > That said, i've been trying to think lately about how to make notmuch a > tool that's usable by normal humans, who probably won't want to > understand all the moving pieces here. I don't want yet another MUA > that requires you to edit a turing-complete config file to get useful > functionality -- we already have mutt for that :) >=20 > Is there a way that we can push this idea/functionality further into > the core of notmuch in a way that makes it easier to use? >=20 > 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): >=20 > notmuch config set new.from_self_tags participated > notmuch config set new.propagate_thread_tags participated >=20 > 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. >=20 > and additionally, if a message was inserted into a thread which has any > of the new.propagated_thread_tags applied, the new message would also > get those tags. >=20 > What do y'all think? >=20 > --dkg > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch