From: Eshel Yaron <me@eshelyaron.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, emacs-devel@gnu.org
Subject: Re: master 4b79c80c999 1/2: New function 'sort-on'
Date: Fri, 02 Feb 2024 17:06:17 +0100 [thread overview]
Message-ID: <m14jeqn952.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <86wmrm50i5.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Feb 2024 17:50:10 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 02 Feb 2024 16:30:03 +0100
>> From: Michael Heerdegen via "Emacs development discussions." <emacs-devel@gnu.org>
>>
>> Here are two more typos, @Eli please review and install if you agree. I
>> guess there could be more, I only have had a quick look at the text:
>
> I already installed other fixes.
Here's one typo that might have slipped by:
diff --git a/doc/lispref/sequences.texi b/doc/lispref/sequences.texi
index 068b69e9ef8..74719d4779f 100644
--- a/doc/lispref/sequences.texi
+++ b/doc/lispref/sequences.texi
@@ -461,7 +461,7 @@ Sequence Functions
with a single argument, an element of @var{sequence}.
This function implements what is known as @dfn{decorate-sort-undecorate}
-paradigm, of the Schwartzian transform. It basically trades CPU for
+paradigm, or the Schwartzian transform. It basically trades CPU for
memory, creating a temporary list with the computed sort keys, then
mapping @code{car} over the result of sorting that temporary list.
Unlike with @code{sort}, the return value is always a new list; the
next prev parent reply other threads:[~2024-02-02 16:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170688047526.14693.2994051491358257471@vcs2.savannah.gnu.org>
[not found] ` <20240202132756.4272CC0EFE7@vcs2.savannah.gnu.org>
2024-02-02 15:00 ` master 4b79c80c999 1/2: New function 'sort-on' Daniel Mendler via Emacs development discussions.
2024-02-02 15:04 ` Eli Zaretskii
2024-02-02 15:26 ` Daniel Mendler via Emacs development discussions.
2024-02-02 15:47 ` Eli Zaretskii
2024-02-02 16:05 ` Daniel Mendler via Emacs development discussions.
2024-02-05 12:14 ` Michael Heerdegen
2024-02-02 15:55 ` Dmitry Gutov
2024-02-02 15:30 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 15:35 ` Daniel Mendler via Emacs development discussions.
2024-02-02 16:08 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 16:23 ` Daniel Mendler via Emacs development discussions.
2024-02-02 16:43 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 15:50 ` Eli Zaretskii
2024-02-02 16:06 ` Eshel Yaron [this message]
2024-02-02 16:34 ` Eli Zaretskii
2024-02-02 16:46 ` Michael Heerdegen via Emacs development discussions.
2024-02-02 17:55 ` Emanuel Berg
2024-02-05 0:48 ` Dmitry Gutov
2024-02-05 5:30 ` Yuri Khan
2024-02-05 12:52 ` Eli Zaretskii
2024-02-05 13:25 ` Dmitry Gutov
2024-02-05 14:31 ` Eli Zaretskii
2024-02-05 14:47 ` Dmitry Gutov
2024-02-05 15:10 ` Eli Zaretskii
2024-02-05 15:29 ` Dmitry Gutov
2024-02-28 7:40 ` Michael Heerdegen
2024-03-01 23:37 ` Dmitry Gutov
2024-03-04 6:45 ` Michael Heerdegen
2024-03-04 16:43 ` Dmitry Gutov
2024-03-05 8:06 ` Michael Heerdegen
2024-03-05 10:21 ` Michael Heerdegen via Emacs development discussions.
2024-03-05 12:39 ` Eli Zaretskii
2024-03-06 3:20 ` Michael Heerdegen
2024-03-06 12:10 ` Eli Zaretskii
2024-03-06 18:34 ` Dmitry Gutov
2024-03-06 20:12 ` John Wiegley
2024-03-07 1:34 ` Dmitry Gutov
2024-03-05 12:44 ` Dmitry Gutov
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=m14jeqn952.fsf@dazzs-mbp.home \
--to=me@eshelyaron.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).