From ef3d40b9011936d616cdb982d5fe25aaeeb54687 Mon Sep 17 00:00:00 2001 From: Yuri D'Elia Date: Thu, 11 Aug 2016 17:54:19 +0200 Subject: [PATCH] Re: Flat search and threaded views --- e3/1db7e49b4aff28ca578cabd84e3efaf8cc74ed | 113 ++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 e3/1db7e49b4aff28ca578cabd84e3efaf8cc74ed diff --git a/e3/1db7e49b4aff28ca578cabd84e3efaf8cc74ed b/e3/1db7e49b4aff28ca578cabd84e3efaf8cc74ed new file mode 100644 index 000000000..439c77699 --- /dev/null +++ b/e3/1db7e49b4aff28ca578cabd84e3efaf8cc74ed @@ -0,0 +1,113 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id 5E5A46DE02A6 + for ; Thu, 11 Aug 2016 08:54:32 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -0.74 +X-Spam-Level: +X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[AWL=-0.729, + 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 SdnNXZaOGmHr for ; + Thu, 11 Aug 2016 08:54:24 -0700 (PDT) +Received: from e.thregr.org (e.thregr.org [80.68.88.20]) + by arlo.cworth.org (Postfix) with ESMTPS id B91AB6DE0281 + for ; Thu, 11 Aug 2016 08:54:23 -0700 (PDT) +Received: from [2a02:27e8:20:9049:56ee:75ff:fe83:444c] (helo=localhost) + by e.thregr.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) + (Exim 4.87) (envelope-from ) id 1bXsJH-0001Zk-B0 + for notmuch@notmuchmail.org; Thu, 11 Aug 2016 17:54:19 +0200 +From: Yuri D'Elia +To: notmuch@notmuchmail.org +Subject: Re: Flat search and threaded views +In-Reply-To: <87eg64bgbg.fsf@wavexx.thregr.org> +References: <87k2fwbl24.fsf@wavexx.thregr.org> <877fbwv6h5.fsf@nikula.org> + <87eg64bgbg.fsf@wavexx.thregr.org> +User-Agent: Notmuch/ (https://notmuchmail.org) Emacs/24.5.1 + (x86_64-pc-linux-gnu) +Date: Thu, 11 Aug 2016 17:54:19 +0200 +Message-ID: <878tw3e1xw.fsf@wavexx.thregr.org> +MIME-Version: 1.0 +Content-Type: text/plain +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.20 +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: Thu, 11 Aug 2016 15:54:32 -0000 + +On Thu, Aug 04 2016, Yuri D'Elia wrote: +> The problem is that the search I've built includes both existing +> messages and unread ones (with a buffer of a day). So even though I get +> a new (unread) message, some existing messages in the thread also match. +> When reading a new thread started within the day, all messages match. + +I've tried to change my workflow to fit notmuch's, for example by +narrowing my default searches only to only match unread messages. + +I'm feeling a bit mixed about the interface. This is not my first +approach to tag-based email management (I actually still use mu4e). I +wanted to give notmuch a try, mostly due to the way tags can be +processed easily with afew. + +I like how the tagging workflow works, actually. I customized afew and +the way default tags are assigned/managed. Batch-processing with afew is +a breeze. I wrote my own plugin to implement MailMove the way I wanted +in a few hours and overridden a few others. I'm quite happy about this. + +I just find the emacs interface a bit confusing. + +- Showing search results in threads, even after narrowing queries, is + not optimal. I'm shown a list of threads which contain tag:unread + messages, *but* the count is the number of messages in the thread + itself. I've been tripped multiple times by this. + + I still think a flat search result would be better. I would like to + jump into the show buffer as it's being done currently (with the whole + thread) for additional context, but not for the direct search results. + +- Tagging individual messages is just cumbersome because of this. I + often flag individual ids that contain things that I need to act on + later. I cannot do this straight from the search results. I need to + read the thread and move the cursor to the appropriate message. + +- Even after reconsidering, I find that '*' will never do what I expect. + I'd like to tag matching ids (that is, what I'm seeing), not threads. + + People often hijack old threads just to find your address. I'm being + shown huge threads, but in reality I'm just getting a new message and + I don't really want to manage threads as well as messages. When + tagging, I almost always tag individual messages. When I tag threads, + generally is to 'kill' them using afew's KillThreadsFilter. + +- The unread mechanism itself is nice, but it doesn't work as you might + expect if you match also read messages. Easier navigation between tags + (such as "jump to the next unread message") is something I'm looking + for. + +- I patched notmuch to sync the TRASHED flag. Yes, deleting is a thing + if you use multiple clients. Would you consider accepting a patch for + this? + +- gnus-alias actually works better than mu4e's "current focus" (which + it's current identity mechanism). mu4e is a bit more comprehensive on + that front, but gnus-alias is smoother, which I didn't expect. + +I didn't still look at the notmuch-search sources. Do you think it would +be hard to support showing individual ids only? Looks like it's easy to +do from the cli, but might require too many conditions in the source. + +mu4e on the other hand offers a guile interface that can be used for +filtering, so I'm not sure which is easier to do :P (implementing afew +with guile, or tweaking notmuch search results). -- 2.26.2