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 1D1586DE1098 for ; Fri, 5 Apr 2019 17:46:35 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.023 X-Spam-Level: X-Spam-Status: No, score=-0.023 tagged_above=-999 required=5 tests=[AWL=-0.022, SPF_PASS=-0.001] 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 FLfaNCIpm25d for ; Fri, 5 Apr 2019 17:46:33 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 9EF9B6DE1097 for ; Fri, 5 Apr 2019 17:46:33 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hCZTY-0000HG-1m; Fri, 05 Apr 2019 20:46:28 -0400 Received: (nullmailer pid 27529 invoked by uid 1000); Sat, 06 Apr 2019 00:46:26 -0000 From: David Bremner To: Sebastian Poeplau , notmuch@notmuchmail.org Subject: Re: notmuch-tag-jump for multiple threads In-Reply-To: <87d0m31eip.fsf@eurecom.fr> References: <87d0m31eip.fsf@eurecom.fr> Date: Fri, 05 Apr 2019 21:46:26 -0300 Message-ID: <87r2agarkt.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Sat, 06 Apr 2019 00:46:35 -0000 Sebastian Poeplau writes: > Hi all, > > I'm wondering which workflow people use for this situation that comes up > frequently for me: I have a search that gives me a bunch of threads, say > new messages from a mailing list, and then I go over them, possibly > reading some threads in detail and skipping over others. Afterwards, I > would like to apply some tag changes to all threads, like "-unread" or > "+archived". So far, the two ways I've found to do so in the search view > are '*' (`notmuch-search-tag-all') and typing the tag change in the > completing read, or marking the entire buffer followed by 'k' > (`notmuch-tag-jump') and the shortcut for my change. It feels as if > something like 'K' would be nice, offering the same jump menu like 'k' > but applying the change to all displayed messages. > > What is your take? Do you ever encounter the same situation? I would > give the implementation a try but wanted to make sure first that I'm not > missing anything. I tend to use '*' for those situations, but that might be because tag-jump was added later. Your proposal sounds ok, as long as it re-uses most of the tag-jump code. On a semi-related note I sometimes miss the ability to mark a set of non-contiguous threads / messages for action (like 'm' in dired).