From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 60639-done@debbugs.gnu.org, one.last.kiss@outlook.com,
drew.adams@oracle.com
Subject: bug#60639: Improvement to the Wording of GNU Emacs Lisp Reference Manual
Date: Wed, 06 Sep 2023 15:50:23 +0300 [thread overview]
Message-ID: <83wmx31n5c.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk=kXNu0sj6W8vNSQUzJKuCgBHMC=LnNK=T6JQ4g+fE7A@mail.gmail.com> (message from Stefan Kangas on Wed, 6 Sep 2023 04:56:18 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 6 Sep 2023 04:56:18 -0700
> Cc: drew.adams@oracle.com, one.last.kiss@outlook.com, 60639@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't mind installing it, but IMO its wording needs some
> > improvement. Here's what I suggest to install:
> >
> > 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{>}. (This is called ``hash notation'' because it
> > begins with the @samp{#} character, known as ``hash'' or ``number
> > sign''). For example:
>
> Looks good to me.
Now installed on the emacs-29 branch, and closing the bug.
next prev parent reply other threads:[~2023-09-06 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 19:41 bug#60639: Improvement to the Wording of GNU Emacs Lisp Reference Manual Xie Shynur
2023-09-05 23:38 ` 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 [this message]
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=83wmx31n5c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60639-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=one.last.kiss@outlook.com \
--cc=stefankangas@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).