From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 41706@debbugs.gnu.org, post+ebugs@guelker.eu
Subject: bug#41706: 26.1; sort-subr predicate cannot be set successfully
Date: Wed, 10 Jun 2020 22:08:21 +0300 [thread overview]
Message-ID: <83k10e68nu.fsf@gnu.org> (raw)
In-Reply-To: <874kriiw6l.fsf@web.de> (message from Michael Heerdegen on Wed, 10 Jun 2020 20:59:30 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: post+ebugs@guelker.eu, 41706@debbugs.gnu.org
> Date: Wed, 10 Jun 2020 20:59:30 +0200
>
> +STARTKEYFUN moves from the start of the record to the start of
> +the key. It may return either a non-nil value to be used as the
> +key, or else the key is a cons (BEG . END) designating the
> +substring of the record between the values of point after
> +STARTKEYFUN and ENDKEYFUN are called. If STARTKEYFUN is nil, the
> +key starts at the beginning of the record.
That's a beginning, thanks. But it needs more work, IMO:
. the cons cell case hints on a possible return value of STARTKEYFUN,
AFAIU, but the text doesn't say so
. the case of STARTKEYFUN being nil is another use case for what
PREDICATE must cope with, and the text should say so
. the text about ENDKEYFUN should also be augmented, IMO
. the description of PREDICATE should reference this text in some
useful way
> BTW, what about the suggestion to support collation order out of the
> box?
What collation would you like to support, and in what form?
next prev parent reply other threads:[~2020-06-10 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 11:09 bug#41706: 26.1; sort-subr predicate cannot be set successfully Marvin Gülker
2020-06-04 12:11 ` Michael Heerdegen
2020-06-04 19:05 ` Marvin Gülker
2020-06-05 8:32 ` Eli Zaretskii
2020-06-05 9:43 ` Michael Heerdegen
2020-06-05 11:43 ` Eli Zaretskii
2020-06-10 18:59 ` Michael Heerdegen
2020-06-10 19:08 ` Eli Zaretskii [this message]
2020-06-11 12:55 ` Michael Heerdegen
2020-06-11 13:39 ` Eli Zaretskii
2020-06-11 13:59 ` Michael Heerdegen
2020-06-11 16:36 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k10e68nu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41706@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=post+ebugs@guelker.eu \
/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://git.savannah.gnu.org/cgit/emacs.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).