From: Ruijie Yu via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "T.V Raman" <raman@google.com>, emacs-devel@gnu.org
Subject: Re: describe-char-fold-equivalences
Date: Sat, 07 Jan 2023 23:59:41 -0600 [thread overview]
Message-ID: <sdvv8lhimyt.fsf@fw.net.yu> (raw)
In-Reply-To: <83k01xr2ml.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>> From: "T.V Raman" <raman@google.com>
>>
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n' that
>> appears on every line as a field delimiter?
>
> Which newlines do you want to get rid of?
>
> If those are the newlines between the individual characters, then
> removing the newlines will produce a single very long line, which will
> be harder to read.
I think they mean for each line, instead of saying "?\N{DESCRIPTION}",
just say "DESCRIPTION".
Best,
RY
next prev parent reply other threads:[~2023-01-08 5:59 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 ` Ruijie Yu via Emacs development discussions. [this message]
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 ` describe-char-fold-equivalences Robert Pluim
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=sdvv8lhimyt.fsf@fw.net.yu \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=raman@google.com \
--cc=ruijie@netyu.xyz \
/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).