--- /dev/null
+Return-Path: <kototamo@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 10309431FBD\r
+ for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:17 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.798\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 2Lr1AzXwOyKy for <notmuch@notmuchmail.org>;\r
+ Tue, 21 Jan 2014 09:07:08 -0800 (PST)\r
+Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com\r
+ [209.85.128.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id C51C2431FAF\r
+ for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:08 -0800 (PST)\r
+Received: by mail-qe0-f41.google.com with SMTP id gc15so4541645qeb.28\r
+ for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:08 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+ :cc:content-type;\r
+ bh=B6hBpCgqsjs10eA6PMmOsdcnFWtnO+ofZhw289hdCQg=;\r
+ b=GmQ23qZQ1IN0cyuuEycLp2badRp98d+E7uCCWu/LISeTPwv8vYUAyKZ13y8lxmsz/m\r
+ 3CgkDLNRAL46dGnJ+7CgFaL/t6RvoFLZZP5aFs8pqtOnvekH+PIuvQVVy8siS1MVPJDX\r
+ TpOys+ODP/preFMnoDdXIqsPwyfR4Uny7M+m/CnR2jzcUNsCWJU+/9hudtFeJ1Vwii/w\r
+ x16iN1w8YOo0i88nNwuoV4DXE8fpS58YmjNW4ycIt6+ALB23OsSZgPhdiU1gEFiN64qw\r
+ zcXYh1e7DvMcCRytRdyVlqKRG8ovyMgaVGeyWJdUKJc3KrwNH8xlX3xVlBt/82A/cBxe\r
+ pIzQ==\r
+MIME-Version: 1.0\r
+X-Received: by 10.140.26.43 with SMTP id 40mr12248032qgu.86.1390324027254;\r
+ Tue, 21 Jan 2014 09:07:07 -0800 (PST)\r
+Received: by 10.229.56.195 with HTTP; Tue, 21 Jan 2014 09:07:07 -0800 (PST)\r
+In-Reply-To: <87fvohs3jw.fsf@zancas.localnet>\r
+References:\r
+ <CADVUuEgnKqsW=gAau2rPkZLkT7j_a5kdTPRmGU23rA_aiMcybA@mail.gmail.com>\r
+ <87iotdfnqy.fsf@raeviah.aidecoe.name> <87sishs9jd.fsf@zancas.localnet>\r
+ <87bnz5fgzc.fsf@raeviah.aidecoe.name> <87fvohs3jw.fsf@zancas.localnet>\r
+Date: Tue, 21 Jan 2014 18:07:07 +0100\r
+Message-ID:\r
+ <CADVUuEiKLPs9tsn7N7BTw0SEodFaDo7mtdn7tsDjRzKVLT=OMA@mail.gmail.com>\r
+Subject: Re: An Emacs Minor Mode to Mute Email Threads\r
+From: kototama kototama <kototamo@gmail.com>\r
+To: David Bremner <david@tethera.net>\r
+Content-Type: multipart/alternative; boundary=001a11c12bf0c46b9b04f07e0930\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 21 Jan 2014 17:07:17 -0000\r
+\r
+--001a11c12bf0c46b9b04f07e0930\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Thanks everyone for the feedback.\r
+\r
+I wasn't aware it could be done on the command line, on the other hand I\r
+really wanted to experiment and see how much notmuch was hackable with\r
+Emacs Lisp.\r
+\r
+\r
+I'll probably explore the command line option for a next version.\r
+\r
+For me it's important that muted thread stay in the inbox, but get their\r
+read tag removed, since I may want to read them later if a colleague points\r
+to me the thread I ignored.\r
+\r
+\r
+On Tue, Jan 21, 2014 at 5:27 PM, David Bremner <david@tethera.net> wrote:\r
+\r
+> Amadeusz =C5=BBo=C5=82nowski <aidecoe@aidecoe.name> writes:\r
+>\r
+> >\r
+> > The question is: should exclude_tags be used in context of killed/mute?\r
+> > This is just for skipping =E2=80=9Einbox=E2=80=9D, not for hiding them =\r
+in all search\r
+> > results - at least IMHO.\r
+> >\r
+>\r
+> For me I definitely want a muted thread to disappear in all searches. I\r
+> have at least three "inboxes" with sometimes overlapping content. But\r
+> yeah, if you don't want that, then you need some other approach than\r
+> exclude_tags. If I understand correctly, what you ask for also sounds\r
+> easily scriptable:\r
+>\r
+> % notmuch tag -inbox +muted -- $(notmuch search --output=3Dthreads\r
+> tag:muted)\r
+>\r
+> and of course that can be done in a post-new script or equivalent.\r
+>\r
+> d\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
+>\r
+\r
+--001a11c12bf0c46b9b04f07e0930\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<div dir=3D"ltr"><div><div><div>Thanks everyone for the feedback.<br><br></=\r
+div>I wasn't aware it could be done on the command line, on the other h=\r
+and I really wanted to experiment and see how much <span style class=3D"">n=\r
+otmuch</span> was hackable with Emacs Lisp.<br>\r
+<br><br></div>I'll probably explore the command line option for a next =\r
+version.<br><br></div>For me it's important that muted thread stay in t=\r
+he inbox, but get their read tag removed, since I may want to read them lat=\r
+er if a colleague points to me the thread I ignored.<br>\r
+</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=\r
+ Jan 21, 2014 at 5:27 PM, David Bremner <span dir=3D"ltr"><<a href=3D"ma=\r
+ilto:david@tethera.net" target=3D"_blank">david@tethera.net</a>></span> =\r
+wrote:<br>\r
+<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=\r
+x #ccc solid;padding-left:1ex"><div class=3D"im">Amadeusz =C5=BBo=C5=82nows=\r
+ki <<a href=3D"mailto:aidecoe@aidecoe.name">aidecoe@aidecoe.name</a>>=\r
+ writes:<br>\r
+<br>\r
+><br>\r
+> The question is: should exclude_tags be used in context of killed/mute=\r
+?<br>\r
+> This is just for skipping =E2=80=9Einbox=E2=80=9D, not for hiding them=\r
+ in all search<br>\r
+> results - at least IMHO.<br>\r
+><br>\r
+<br>\r
+</div>For me I definitely want a muted thread to disappear in all searches.=\r
+ I<br>\r
+have at least three "inboxes" with sometimes overlapping content.=\r
+ But<br>\r
+yeah, if you don't want that, then you need some other approach than<br=\r
+>\r
+exclude_tags. If I understand correctly, what you ask for also sounds<br>\r
+easily scriptable:<br>\r
+<br>\r
+=C2=A0 % notmuch tag -inbox +muted -- $(notmuch search --output=3Dthreads t=\r
+ag:muted)<br>\r
+<br>\r
+and of course that can be done in a post-new script or equivalent.<br>\r
+<br>\r
+d<br>\r
+_______________________________________________<br>\r
+notmuch mailing list<br>\r
+<a href=3D"mailto:notmuch@notmuchmail.org">notmuch@notmuchmail.org</a><br>\r
+<a href=3D"http://notmuchmail.org/mailman/listinfo/notmuch" target=3D"_blan=\r
+k">http://notmuchmail.org/mailman/listinfo/notmuch</a><br>\r
+</blockquote></div><br></div>\r
+\r
+--001a11c12bf0c46b9b04f07e0930--\r
projects / notmuch-archives.git / commitdiff