unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Christopher Dimech <dimech@gmx.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
	uzibalqa <uzibalqa@proton.me>,
	64692@debbugs.gnu.org
Subject: bug#64692: Better descriptions of Cons Cells and Dotted Notation with real-life syntax
Date: Tue, 18 Jul 2023 21:24:21 +0800	[thread overview]
Message-ID: <874jm15p4q.fsf@yahoo.com> (raw)
In-Reply-To: <trinity-78c253f9-763f-4c19-b328-d0644611868e-1689685102784@3c-app-mailcom-bs07> (Christopher Dimech's message of "Tue, 18 Jul 2023 14:58:22 +0200")

Christopher Dimech <dimech@gmx.com> writes:

> Reading it does not mean understanding it !

There is no space in any Emacs manual to repeatedly explain basic Lisp
reader syntax every time it is used.





  reply	other threads:[~2023-07-18 13:24 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 [this message]
2023-07-18 17:20   ` Drew Adams
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=874jm15p4q.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64692@debbugs.gnu.org \
    --cc=dimech@gmx.com \
    --cc=luangruo@yahoo.com \
    --cc=uzibalqa@proton.me \
    --cc=yantar92@posteo.net \
    /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).