all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 15:16:58 +0100	[thread overview]
Message-ID: <87ilhfhjxh.fsf@gmail.com> (raw)
In-Reply-To: <p911qo5f4zy.fsf@google.com> (T. V. Raman's message of "Sun, 08 Jan 2023 06:57:53 -0800")

>>>>> On Sun, 08 Jan 2023 06:57:53 -0800, "T.V Raman" <raman@google.com> said:

    TVR> Yuri Khan <yuri.v.khan@gmail.com> writes:
    TVR> It did make it obvious, the me the user still got confused -- I wasn't
    TVR> aware of that particular usage 

See (info "(elisp) General Escape Syntax")

The idea was to produce something that people could copy and use,
without having the unicode codepoint numbers appearing.

Robert
-- 



  reply	other threads:[~2023-01-09 14:16 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     ` Robert Pluim [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilhfhjxh.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.