unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: William Casarin <jb55@jb55.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Proposed New sort API
Date: Mon, 08 Oct 2018 20:05:17 -0700	[thread overview]
Message-ID: <87d0sj6cr6.fsf@jb55.com> (raw)
In-Reply-To: <20171210154956.4049-1-david@tethera.net>

David Bremner <david@tethera.net> writes:

> I started looking at William's sorting patches [1], but the
> proliferation of sorting options bugged me a bit. I decided to sketch
> out a new more flexible API.
>
> In the new API, there is is a sort "key", currently mapped one-to-one
> to value slots, but potentially could do more sophisticated things
> like making keys up dynamically (e.g. preprocessing subjects).
>
> The second parameter is a sort "type". Currently this is just
> ascending or descending, but other potential options include
> sort_by_relevance_then_value


Another thought I had that I wanted to throw out there for
consideration. It would be nice to be able to sort by "popular" threads,
aka sort by the number of messages in each thread. Not sure if this is
an easy thing to do at the query level?


Cheers,
Will

  parent reply	other threads:[~2018-10-09  3:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 15:49 Proposed New sort API David Bremner
2017-12-10 15:49 ` [PATCH 1/2] WIP: groundwork for new sorting API David Bremner
2018-10-08 20:51   ` William Casarin
2018-10-20 11:51     ` David Bremner
2017-12-10 15:49 ` [PATCH 2/2] WIP: use new sort key/type David Bremner
2017-12-10 19:37 ` Proposed New sort API William Casarin
2018-10-09  3:05 ` William Casarin [this message]
2018-10-20 11:43   ` David Bremner
2018-10-20 17:15     ` William Casarin
2018-10-21 11:44       ` David Bremner

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=87d0sj6cr6.fsf@jb55.com \
    --to=jb55@jb55.com \
    --cc=david@tethera.net \
    --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).