From: "T.V Raman" <raman@google.com>
To: emacs-devel@gnu.org
Subject: describe-char-fold-equivalences
Date: Sat, 07 Jan 2023 20:26:44 -0800 [thread overview]
Message-ID: <p91eds5fy7v.fsf@google.com> (raw)
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?
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
': ?\N{APOSTROPHE}
❟: ?\N{HEAVY LOW SINGLE COMMA QUOTATION MARK ORNAMENT}
❛: ?\N{HEAVY SINGLE TURNED COMMA QUOTATION MARK ORNAMENT}
❜: ?\N{HEAVY SINGLE COMMA QUOTATION MARK ORNAMENT}
‘: ?\N{LEFT SINGLE QUOTATION MARK}
’: ?\N{RIGHT SINGLE QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
‛: ?\N{SINGLE HIGH-REVERSED-9 QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
: ?\N{TAG QUOTATION MARK}
❮: ?\N{HEAVY LEFT-POINTING ANGLE QUOTATION MARK ORNAMENT}
❯: ?\N{HEAVY RIGHT-POINTING ANGLE QUOTATION MARK ORNAMENT}
‹: ?\N{SINGLE LEFT-POINTING ANGLE QUOTATION MARK}
›: ?\N{SINGLE RIGHT-POINTING ANGLE QUOTATION MARK}
': ?\N{FULLWIDTH APOSTROPHE}
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next reply other threads:[~2023-01-08 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 4:26 T.V Raman [this message]
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 ` 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=p91eds5fy7v.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@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).