From: Ulrich Mueller <ulm@gentoo.org>
To: 72486@debbugs.gnu.org
Subject: bug#72486: 31.0.50; string> not documented in the lispref manual
Date: Tue, 06 Aug 2024 06:22:34 +0200 [thread overview]
Message-ID: <uzfpqz3ed@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 148 bytes --]
Section 4.5 "Comparison of Characters and Strings" has string<,
string-lessp and string-greaterp, but string> is missing.
Trivial patch attached.
[-- Attachment #2: 0001-doc-lispref-strings.texi-Text-Comparison-Document-st.patch --]
[-- Type: text/plain, Size: 1108 bytes --]
From eab9317546b5d7d7e66668a7cf1e77a4a69d052f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@gentoo.org>
Date: Tue, 6 Aug 2024 06:18:53 +0200
Subject: [PATCH] * doc/lispref/strings.texi (Text Comparison): Document
'string>'.
---
doc/lispref/strings.texi | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index 06094e45aad..36974b9e4b5 100644
--- a/doc/lispref/strings.texi
+++ b/doc/lispref/strings.texi
@@ -655,10 +655,14 @@ Text Comparison
@code{string-lessp} is another name for @code{string<}.
@end defun
-@defun string-greaterp string1 string2
+@defun string> string1 string2
This function returns the result of comparing @var{string1} and
@var{string2} in the opposite order, i.e., it is equivalent to calling
-@code{(string-lessp @var{string2} @var{string1})}.
+@code{(string< @var{string2} @var{string1})}.
+@end defun
+
+@defun string-greaterp string1 string2
+@code{string-greaterp} is another name for @code{string>}.
@end defun
@cindex locale-dependent string comparison
--
2.45.2
next reply other threads:[~2024-08-06 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 4:22 Ulrich Mueller [this message]
2024-08-06 11:45 ` bug#72486: 31.0.50; string> not documented in the lispref manual Eli Zaretskii
2024-08-06 16:08 ` Ulrich Mueller
2024-08-06 16:27 ` 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=uzfpqz3ed@gentoo.org \
--to=ulm@gentoo.org \
--cc=72486@debbugs.gnu.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://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).