From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode
Date: Fri, 14 Oct 2022 20:42:39 +0300 [thread overview]
Message-ID: <83zgdy714g.fsf@gnu.org> (raw)
In-Reply-To: <87mt9yxtvi.fsf@gmail.com> (message from Robert Pluim on Fri, 14 Oct 2022 18:17:05 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 14 Oct 2022 18:17:05 +0200
>
> >>>>> On Fri, 14 Oct 2022 18:56:35 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> IMO, if we think this alternative needs to be described in the Emacs
> Eli> manual, we should describe it, not cross-link to the ELisp manual.
> Eli> References to ELisp are only justified when they refer to Lisp code or
> Eli> details of some functions or variables, not to user commands.
>
> Hmm, so move or copy "General Escape Syntax" under
> (emacs)International somewhere, and refer to it from the "You can
> insert non-ASCII characters or search for them" section of that node
> (since thatʼs where we talk about C-x 8)?
Yes, something like that.
next prev parent reply other threads:[~2022-10-14 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 15:56 emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode Eli Zaretskii
2022-10-14 16:17 ` Robert Pluim
2022-10-14 17:42 ` Eli Zaretskii [this message]
2022-10-18 15:05 ` Robert Pluim
2022-10-18 15:18 ` Eli Zaretskii
2022-10-18 15:58 ` Eli Zaretskii
2022-10-18 16:06 ` Robert Pluim
2022-10-21 19:42 ` Richard Stallman
2022-10-22 6:19 ` Eli Zaretskii
2022-10-22 7:43 ` Po Lu
2022-10-22 20:05 ` Richard Stallman
2022-10-24 4:40 ` Christopher Dimech
2022-10-24 13:06 ` Eli Zaretskii
2022-10-22 17:22 ` [External] : " Drew Adams
2022-10-24 3:05 ` RE: [External] : " Christopher Dimech
2022-10-22 20:06 ` Richard Stallman
2022-10-23 5:15 ` Eli Zaretskii
2022-10-24 19:31 ` Richard Stallman
2022-10-24 19:44 ` Eli Zaretskii
2022-10-24 19:57 ` Christopher Dimech
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=83zgdy714g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).