From: Leonard Lausen <leonard@lausen.nl>
To: notmuch@notmuchmail.org
Subject: Sorting & grouping
Date: Sat, 21 Jul 2018 21:57:17 +0000 [thread overview]
Message-ID: <87muuk6yma.fsf@lausen.nl> (raw)
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
next reply other threads:[~2018-07-21 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 21:57 Leonard Lausen [this message]
2018-07-23 14:46 ` Sorting & grouping William Casarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muuk6yma.fsf@lausen.nl \
--to=leonard@lausen.nl \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).