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 573E66DE01E7 for ; Sat, 21 Jul 2018 15:54:47 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 w9uSo2uzK2Sd for ; Sat, 21 Jul 2018 15:54:45 -0700 (PDT) Received: from slow1-d.mail.gandi.net (mslow2.mail.gandi.net [217.70.178.242]) by arlo.cworth.org (Postfix) with ESMTPS id 370E16DE00D1 for ; Sat, 21 Jul 2018 15:54:44 -0700 (PDT) Received: from relay8-d.mail.gandi.net (unknown [217.70.183.201]) by slow1-d.mail.gandi.net (Postfix) with ESMTP id 46A413A1F33 for ; Sat, 21 Jul 2018 23:57:25 +0200 (CEST) X-Originating-IP: 76.102.151.26 Received: from localhost (c-76-102-151-26.hsd1.ca.comcast.net [76.102.151.26]) (Authenticated sender: leonard@lausen.nl) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 60F901BF204 for ; Sat, 21 Jul 2018 21:57:19 +0000 (UTC) From: Leonard Lausen To: notmuch@notmuchmail.org Cc: Subject: Sorting & grouping Date: Sat, 21 Jul 2018 21:57:17 +0000 Message-ID: <87muuk6yma.fsf@lausen.nl> MIME-Version: 1.0 Content-Type: text/plain X-Mailman-Approved-At: Sat, 21 Jul 2018 22:35:55 -0700 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 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, 21 Jul 2018 22:54:47 -0000 There have been some previous discussions about introducing more sorting options: id:87r2vmw6ev.fsf@jb55.com id:87a82aip0d.fsf@jb55.com David has also proposed a new sort API in id:20171210154956.4049-1-david@tethera.net I believe the initial use-case of William was to sort incoming Github notifications by project? The reasoning may be that less context switches are necessary while going through the list of unread threads, which by default would be sorted by date and may mix the threads of potentially many projects. One workaround would be to issue one search per project in sequence, but this can quickly become unwieldly as the number of projects grows. For this use-case, it seems the notion of "Grouping" results in the notmuch-search view may be helpful. Consider all Github mails being tagged with 'software' as well as 'lists/$PROJECT_NAME'. Then, currently a search for 'tag:software tag:unread' will mix threads from different projects, sorting all by date. What do you think about adding a 'group' option that will group mails with the same set of tags (possibly minus a list of tags to be ignored when grouping) and apply the normal search order (e.g. by date) within each group? Or is this already possible? Best regards Leonard