From: Daniel Schoepe <daniel@schoepe.org>
To: Jani Nikula <jani@nikula.org>,
Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v2] emacs: Pass a copy to notmuch-saved-search-sort-function
Date: Mon, 05 Mar 2012 22:08:39 +0100 [thread overview]
Message-ID: <87y5rekb6w.fsf@schoepe.localhost> (raw)
In-Reply-To: <CAB+hUn-iQbXq_UDcj97h2Duq=gJdxpiJjOn6YzmVcZw+GEgK0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
On Mar 5, 2012 5:43 PM, "Dmitry Kurochkin" <dmitry.kurochkin@gmail.com>
> I do not buy the argument that we should help users who implement their
> own sorting functions but do not read documentation for functions they
> use. Apparently, those who implemented the `sort' function had similar
> ideas. And I do not think it is our job to add workarounds for it.
Yeah that also sounds a bit more consistent, I guess my perception was
colored by my surprise at learning that sort has side effects in elisp. :)
On Mon, 5 Mar 2012 22:55:54 +0200, Jani Nikula <jani@nikula.org> wrote:
> Providing the customization of the sort function is more powerful than the
> compare function. In the case of saved searches I can imagine people might
> want to partially use the original order while sort the rest (e.g.
> important ones first in predefined order, others sorted). In fact this also
> allows dropping out some elements. And renaming. And changing the queries...
>
> (I had something like that in mind originally but then settled with just
> capitalizing the important ones to show them first.)
I have the same objections to only providing a customization option for
comparing.
Cheers,
Daniel
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-03-05 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:44 [PATCH 0/1] emacs: Pass a copy to notmuch-saved-search-sort-function Daniel Schoepe
2012-03-01 14:44 ` [PATCH] " Daniel Schoepe
2012-03-05 20:55 ` [PATCH v2] " Jani Nikula
2012-03-05 21:08 ` Daniel Schoepe [this message]
2012-03-05 21:09 ` Dmitry Kurochkin
2012-03-06 8:20 ` Jani Nikula
2012-03-01 20:24 ` [PATCH v2 0/1] " Daniel Schoepe
2012-03-01 20:24 ` [PATCH v2] " Daniel Schoepe
2012-03-03 21:36 ` Jani Nikula
2012-03-05 2:21 ` Dmitry Kurochkin
2012-03-05 11:17 ` Daniel Schoepe
2012-03-05 15:23 ` Tomi Ollila
2012-03-05 15:42 ` Dmitry Kurochkin
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=87y5rekb6w.fsf@schoepe.localhost \
--to=daniel@schoepe.org \
--cc=dmitry.kurochkin@gmail.com \
--cc=jani@nikula.org \
--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).