From: Xie Shynur <one.last.kiss@outlook.com>
To: 60639@debbugs.gnu.org
Subject: bug#60639: Improvement to the Wording of GNU Emacs Lisp Reference Manual
Date: Sat, 7 Jan 2023 19:41:17 +0000 [thread overview]
Message-ID: <SA0PR04MB74332E259688725FF02B5A60D7F89@SA0PR04MB7433.namprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
In the section 2.1 "Printed Representation and Read Syntax" (https://www.gnu.org/software/emacs/manual/html_node/elisp/Printed-Representation.html), word "hash notation" is used to refer to the symbol "#".
But it may well confuse non-native English speakers, because the "hash" is also associated with "hash function".
A better name for "#" is "number sign".
[-- Attachment #2: 0001-better-word-for-hash-notation.patch --]
[-- Type: application/octet-stream, Size: 1275 bytes --]
From d576b9ee6c824cf55b478c06a1f2644d8220d4be Mon Sep 17 00:00:00 2001
From: Shynur <one.last.kiss@outlook.com>
Date: Sun, 8 Jan 2023 03:32:00 +0800
Subject: [PATCH] better word for hash notation''
---
doc/lispref/objects.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
index 99a3c07397..39be94b4a8 100644
--- a/doc/lispref/objects.texi
+++ b/doc/lispref/objects.texi
@@ -79,10 +79,10 @@ syntax. @xref{Read and Print}.
In most cases, an object's printed representation is also a read
syntax for the object. However, some types have no read syntax, since
it does not make sense to enter objects of these types as constants in
-a Lisp program. These objects are printed in @dfn{hash notation},
-which consists of the characters @samp{#<}, a descriptive string
-(typically the type name followed by the name of the object), and a
-closing @samp{>}. For example:
+a Lisp program. These objects are printed in @dfn{hash notation}
+(also known as ``number sign''), which consists of the characters
+@samp{#<}, a descriptive string (typically the type name followed by
+the name of the object), and a closing @samp{>}. For example:
@example
(current-buffer)
--
2.38.0.windows.1
next reply other threads:[~2023-01-07 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 19:41 Xie Shynur [this message]
2023-09-05 23:38 ` bug#60639: Improvement to the Wording of GNU Emacs Lisp Reference Manual Stefan Kangas
2023-09-06 1:27 ` Drew Adams
2023-09-06 1:33 ` Drew Adams
2023-09-06 1:46 ` Stefan Kangas
2023-09-06 11:52 ` Eli Zaretskii
2023-09-06 11:56 ` Stefan Kangas
2023-09-06 12:50 ` Eli Zaretskii
2023-09-06 7:58 ` Visuwesh
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=SA0PR04MB74332E259688725FF02B5A60D7F89@SA0PR04MB7433.namprd04.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=60639@debbugs.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).