all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:56:35 +0300	[thread overview]
Message-ID: <831qra8klo.fsf@gnu.org> (raw)

> +  An alternative to using non-@acronym{ASCII} characters directly is
> +to use one of the character escape syntaxes described in
> +@pxref{General Escape Syntax,,, elisp, The Emacs Lisp Reference
> +Manual}, as they allow all Unicode codepoints to be specified using
> +only @acronym{ASCII} characters.

IMO, if we think this alternative needs to be described in the Emacs
manual, we should describe it, not cross-link to the ELisp manual.
References to ELisp are only justified when they refer to Lisp code or
details of some functions or variables, not to user commands.



             reply	other threads:[~2022-10-14 15:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 15:56 Eli Zaretskii [this message]
2022-10-14 16:17 ` emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode Robert Pluim
2022-10-14 17:42   ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=831qra8klo.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 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.