1 Return-Path: <kototamo@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 10309431FBD
\r
6 for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:17 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7]
\r
15 Received: from olra.theworths.org ([127.0.0.1])
\r
16 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id 2Lr1AzXwOyKy for <notmuch@notmuchmail.org>;
\r
18 Tue, 21 Jan 2014 09:07:08 -0800 (PST)
\r
19 Received: from mail-qe0-f41.google.com (mail-qe0-f41.google.com
\r
20 [209.85.128.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id C51C2431FAF
\r
23 for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:08 -0800 (PST)
\r
24 Received: by mail-qe0-f41.google.com with SMTP id gc15so4541645qeb.28
\r
25 for <notmuch@notmuchmail.org>; Tue, 21 Jan 2014 09:07:08 -0800 (PST)
\r
26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
27 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
29 bh=B6hBpCgqsjs10eA6PMmOsdcnFWtnO+ofZhw289hdCQg=;
\r
30 b=GmQ23qZQ1IN0cyuuEycLp2badRp98d+E7uCCWu/LISeTPwv8vYUAyKZ13y8lxmsz/m
\r
31 3CgkDLNRAL46dGnJ+7CgFaL/t6RvoFLZZP5aFs8pqtOnvekH+PIuvQVVy8siS1MVPJDX
\r
32 TpOys+ODP/preFMnoDdXIqsPwyfR4Uny7M+m/CnR2jzcUNsCWJU+/9hudtFeJ1Vwii/w
\r
33 x16iN1w8YOo0i88nNwuoV4DXE8fpS58YmjNW4ycIt6+ALB23OsSZgPhdiU1gEFiN64qw
\r
34 zcXYh1e7DvMcCRytRdyVlqKRG8ovyMgaVGeyWJdUKJc3KrwNH8xlX3xVlBt/82A/cBxe
\r
37 X-Received: by 10.140.26.43 with SMTP id 40mr12248032qgu.86.1390324027254;
\r
38 Tue, 21 Jan 2014 09:07:07 -0800 (PST)
\r
39 Received: by 10.229.56.195 with HTTP; Tue, 21 Jan 2014 09:07:07 -0800 (PST)
\r
40 In-Reply-To: <87fvohs3jw.fsf@zancas.localnet>
\r
42 <CADVUuEgnKqsW=gAau2rPkZLkT7j_a5kdTPRmGU23rA_aiMcybA@mail.gmail.com>
\r
43 <87iotdfnqy.fsf@raeviah.aidecoe.name> <87sishs9jd.fsf@zancas.localnet>
\r
44 <87bnz5fgzc.fsf@raeviah.aidecoe.name> <87fvohs3jw.fsf@zancas.localnet>
\r
45 Date: Tue, 21 Jan 2014 18:07:07 +0100
\r
47 <CADVUuEiKLPs9tsn7N7BTw0SEodFaDo7mtdn7tsDjRzKVLT=OMA@mail.gmail.com>
\r
48 Subject: Re: An Emacs Minor Mode to Mute Email Threads
\r
49 From: kototama kototama <kototamo@gmail.com>
\r
50 To: David Bremner <david@tethera.net>
\r
51 Content-Type: multipart/alternative; boundary=001a11c12bf0c46b9b04f07e0930
\r
52 Cc: notmuch@notmuchmail.org
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Tue, 21 Jan 2014 17:07:17 -0000
\r
67 --001a11c12bf0c46b9b04f07e0930
\r
68 Content-Type: text/plain; charset=UTF-8
\r
69 Content-Transfer-Encoding: quoted-printable
\r
71 Thanks everyone for the feedback.
\r
73 I wasn't aware it could be done on the command line, on the other hand I
\r
74 really wanted to experiment and see how much notmuch was hackable with
\r
78 I'll probably explore the command line option for a next version.
\r
80 For me it's important that muted thread stay in the inbox, but get their
\r
81 read tag removed, since I may want to read them later if a colleague points
\r
82 to me the thread I ignored.
\r
85 On Tue, Jan 21, 2014 at 5:27 PM, David Bremner <david@tethera.net> wrote:
\r
87 > Amadeusz =C5=BBo=C5=82nowski <aidecoe@aidecoe.name> writes:
\r
90 > > The question is: should exclude_tags be used in context of killed/mute?
\r
91 > > This is just for skipping =E2=80=9Einbox=E2=80=9D, not for hiding them =
\r
93 > > results - at least IMHO.
\r
96 > For me I definitely want a muted thread to disappear in all searches. I
\r
97 > have at least three "inboxes" with sometimes overlapping content. But
\r
98 > yeah, if you don't want that, then you need some other approach than
\r
99 > exclude_tags. If I understand correctly, what you ask for also sounds
\r
100 > easily scriptable:
\r
102 > % notmuch tag -inbox +muted -- $(notmuch search --output=3Dthreads
\r
105 > and of course that can be done in a post-new script or equivalent.
\r
108 > _______________________________________________
\r
109 > notmuch mailing list
\r
110 > notmuch@notmuchmail.org
\r
111 > http://notmuchmail.org/mailman/listinfo/notmuch
\r
114 --001a11c12bf0c46b9b04f07e0930
\r
115 Content-Type: text/html; charset=UTF-8
\r
116 Content-Transfer-Encoding: quoted-printable
\r
118 <div dir=3D"ltr"><div><div><div>Thanks everyone for the feedback.<br><br></=
\r
119 div>I wasn't aware it could be done on the command line, on the other h=
\r
120 and I really wanted to experiment and see how much <span style class=3D"">n=
\r
121 otmuch</span> was hackable with Emacs Lisp.<br>
\r
122 <br><br></div>I'll probably explore the command line option for a next =
\r
123 version.<br><br></div>For me it's important that muted thread stay in t=
\r
124 he inbox, but get their read tag removed, since I may want to read them lat=
\r
125 er if a colleague points to me the thread I ignored.<br>
\r
126 </div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
\r
127 Jan 21, 2014 at 5:27 PM, David Bremner <span dir=3D"ltr"><<a href=3D"ma=
\r
128 ilto:david@tethera.net" target=3D"_blank">david@tethera.net</a>></span> =
\r
130 <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
\r
131 x #ccc solid;padding-left:1ex"><div class=3D"im">Amadeusz =C5=BBo=C5=82nows=
\r
132 ki <<a href=3D"mailto:aidecoe@aidecoe.name">aidecoe@aidecoe.name</a>>=
\r
136 > The question is: should exclude_tags be used in context of killed/mute=
\r
138 > This is just for skipping =E2=80=9Einbox=E2=80=9D, not for hiding them=
\r
140 > results - at least IMHO.<br>
\r
143 </div>For me I definitely want a muted thread to disappear in all searches.=
\r
145 have at least three "inboxes" with sometimes overlapping content.=
\r
147 yeah, if you don't want that, then you need some other approach than<br=
\r
149 exclude_tags. If I understand correctly, what you ask for also sounds<br>
\r
150 easily scriptable:<br>
\r
152 =C2=A0 % notmuch tag -inbox +muted -- $(notmuch search --output=3Dthreads t=
\r
155 and of course that can be done in a post-new script or equivalent.<br>
\r
158 _______________________________________________<br>
\r
159 notmuch mailing list<br>
\r
160 <a href=3D"mailto:notmuch@notmuchmail.org">notmuch@notmuchmail.org</a><br>
\r
161 <a href=3D"http://notmuchmail.org/mailman/listinfo/notmuch" target=3D"_blan=
\r
162 k">http://notmuchmail.org/mailman/listinfo/notmuch</a><br>
\r
163 </blockquote></div><br></div>
\r
165 --001a11c12bf0c46b9b04f07e0930--
\r