From: Drew Adams <drew.adams@oracle.com>
To: Po Lu <luangruo@yahoo.com>, uzibalqa <uzibalqa@proton.me>
Cc: "64692-done@debbugs.gnu.org" <64692-done@debbugs.gnu.org>
Subject: bug#64692: Better descriptions of Cons Cells and Dotted Notation with real-life syntax
Date: Tue, 18 Jul 2023 17:20:02 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488139D25D6C661585325C4F338A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87jzux5x2g.fsf@yahoo.com>
> The node containing your example is located in the Emacs Lisp reference
> manual, which contains two adequate descriptions of both dotted lists
> and dotted pair notation.
Yes, it does.
But a reader of this menu-syntax node
won't have a clue about that. Please
provide a cross-reference to it.
Defining menus is one of the first
places a new Elisp user will run into
dot-notation syntax.
Another is the complex syntax for
font-lock. There too a reader will
need to understand dot notation to
make sense of the syntax spec.
> I see no problem here; closing.
That's too bad.
next prev parent reply other threads:[~2023-07-18 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 20:17 bug#64692: Better descriptions of Cons Cells and Dotted Notation with real-life syntax uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 10:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 10:36 ` Ihor Radchenko
2023-07-18 12:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 12:58 ` Christopher Dimech
2023-07-18 13:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 17:20 ` Drew Adams [this message]
2023-07-18 17:32 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 10:54 ` Eli Zaretskii
2023-07-18 11:19 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 17:13 ` Drew Adams
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=SJ0PR10MB5488139D25D6C661585325C4F338A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=64692-done@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=uzibalqa@proton.me \
/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).