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: Fri, 05 Jun 2020 14:43:39 +0300 [thread overview]
Message-ID: <83a71hbuvo.fsf@gnu.org> (raw)
In-Reply-To: <87h7vpg85k.fsf@web.de> (message from Michael Heerdegen on Fri, 05 Jun 2020 11:43:19 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Marvin Gülker <post+ebugs@guelker.eu>,
> 41706@debbugs.gnu.org
> Date: Fri, 05 Jun 2020 11:43:19 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It is hard to be specific about the arguments to PREDICATE, because
> > they depend on what the other arguments to sort-subr return. I
> > augmented the manual to at least have the same information as the doc
> > string; more detail is only possible if we discuss specific values of
> > STARTKEYFUN and ENDKEYFUN.
>
> But this sentence is not correct:
>
> "It [i.e. STARTKEYFUN, added by me] may return either a non-nil value to
> be used as the key, or else the key is the substring between the values
> of point after STARTKEYFUN and ENDKEYFUN are called."
I didn't change that part.
> This is the sentence that misled the OP I think. Could we be more
> precise and tell that the key is actually the cons cell (BEG . END)
> denoting these strings?
Patches welcome.
next prev parent reply other threads:[~2020-06-05 11:43 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 [this message]
2020-06-10 18:59 ` Michael Heerdegen
2020-06-10 19:08 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a71hbuvo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.