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

I wasn't aware it could be done on the command line, on the other h= and I really wanted to experiment and see how much n= otmuch was hackable with Emacs Lisp.


I'll probably explore the command line option for a next = version.

For me it's important that muted thread stay in t= he inbox, but get their read tag removed, since I may want to read them lat= er if a colleague points to me the thread I ignored.


On Tue,= Jan 21, 2014 at 5:27 PM, David Bremner <david@tethera.net> = wrote:
Amadeusz =C5=BBo=C5=82nows= ki <aidecoe@aidecoe.name>= writes:

>
> The question is: should exclude_tags be used in context of killed/mute= ?
> This is just for skipping =E2=80=9Einbox=E2=80=9D, not for hiding them= in all search
> results - at least IMHO.
>

For me I definitely want a muted thread to disappear in all searches.= I
have at least three "inboxes" with sometimes overlapping content.= But
yeah, if you don't want that, then you need some other approach than exclude_tags. If I understand correctly, what you ask for also sounds
easily scriptable:

=C2=A0 % notmuch tag -inbox +muted -- $(notmuch search --output=3Dthreads t= ag:muted)

and of course that can be done in a post-new script or equivalent.

d
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

--001a11c12bf0c46b9b04f07e0930--