From: Robert Pluim <rpluim@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: Yuri Khan <yuri.v.khan@gmail.com>, emacs-devel@gnu.org
Subject: Re: describe-char-fold-equivalences
Date: Mon, 09 Jan 2023 16:54:01 +0100 [thread overview]
Message-ID: <87a62rhffq.fsf@gmail.com> (raw)
In-Reply-To: <p91eds33et6.fsf@google.com> (T. V. Raman's message of "Mon, 09 Jan 2023 07:31:17 -0800")
>>>>> On Mon, 09 Jan 2023 07:31:17 -0800, "T.V Raman" <raman@google.com> said:
T> thanks for the explanation.
T> Perhaps we could make that more discoverable when reading the output of
T> that function ie the doc string I complained about?
Yes. Something like this for emacs-29?
diff --git a/lisp/char-fold.el b/lisp/char-fold.el
index eff2f5558b3..f1da7997407 100644
--- a/lisp/char-fold.el
+++ b/lisp/char-fold.el
@@ -436,7 +436,24 @@ describe-char-fold-equivalences
describe all available character equivalences of `char-fold-to-regexp'.
Optional argument LAX (interactively, the prefix argument), if
non-nil, means also include partially matching ligatures and
-non-canonical equivalences."
+non-canonical equivalences.
+
+Each line of the display shows the equivalences in two different
+ways separated by a colon:
+
+ - as the literal character or sequence
+ - using an ASCII-only escape syntax
+
+For example, for the letter 'r', the first line is
+
+ r: ?\N{LATIN SMALL LETTER R}
+
+which is for the requested character itself, and a later line has
+
+ ṟ: ?\N{LATIN SMALL LETTER R}?\N{COMBINING MACRON BELOW}
+
+which clearly shows what the constituent characters are."
(interactive (list (ignore-errors
(read-char-by-name
(format-prompt "Unicode name, single char, or hex"
next prev parent reply other threads:[~2023-01-09 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 4:26 describe-char-fold-equivalences T.V Raman
2023-01-08 5:56 ` describe-char-fold-equivalences Eli Zaretskii
2023-01-08 5:59 ` describe-char-fold-equivalences Ruijie Yu via Emacs development discussions.
2023-01-08 14:57 ` describe-char-fold-equivalences T.V Raman
2023-01-08 14:55 ` describe-char-fold-equivalences T.V Raman
2023-01-08 6:02 ` describe-char-fold-equivalences Yuri Khan
2023-01-08 14:57 ` describe-char-fold-equivalences T.V Raman
2023-01-09 14:16 ` describe-char-fold-equivalences Robert Pluim
2023-01-09 15:31 ` describe-char-fold-equivalences T.V Raman
2023-01-09 15:54 ` Robert Pluim [this message]
2023-01-09 18:31 ` describe-char-fold-equivalences T.V Raman
2023-01-10 16:16 ` describe-char-fold-equivalences Robert Pluim
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=87a62rhffq.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=yuri.v.khan@gmail.com \
/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).