From: Drew Adams <drew.adams@oracle.com>
To: Alan Mackenzie <acm@muc.de>, 30217@debbugs.gnu.org
Subject: bug#30217: Ambiguity in NEWS in emacs-26.0.91
Date: Mon, 22 Jan 2018 14:42:34 -0800 (PST) [thread overview]
Message-ID: <5074511f-b3b3-45aa-80b4-130be08f30ec@default> (raw)
In-Reply-To: <20180122221743.GB4888@ACM>
> In the new NEWS in the recent pretest, at L1381 we have:
>
> ** To avoid confusion caused by "smart quotes", the reader no longer
> accepts Lisp symbols which begin with the following quotation
> characters: `'"" , unless they are escaped with backslash.
> ^^^^
>
> , which leaves it unclear whether it's the "smart quotes" or the Lisp
> symbols which need escaping.
>
> I suggest replacing "they" with either "these quotes" or "these symbols"
> depending on the desired meaning.
Even if that ambiguity gets resolved, I have no idea what
the text means. What does it mean for the Lisp reader to
"accept a Lisp symbol"?
Please describe exactly what the reader does when it reads
one of those characters followed by Lisp-symbol syntax, in
both cases: char escaped and char not escaped.
next prev parent reply other threads:[~2018-01-22 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:17 bug#30217: Ambiguity in NEWS in emacs-26.0.91 Alan Mackenzie
2018-01-22 22:42 ` Drew Adams [this message]
2018-01-23 0:42 ` Noam Postavsky
2018-01-23 0:56 ` Drew Adams
2018-01-23 1:40 ` Noam Postavsky
2018-01-23 6:07 ` Drew Adams
2018-01-23 6:21 ` Drew Adams
2018-01-23 12:54 ` Noam Postavsky
2018-01-23 15:53 ` Drew Adams
2018-01-23 23:00 ` Noam Postavsky
2018-01-23 23:19 ` Drew Adams
2018-01-24 0:02 ` Noam Postavsky
2018-01-28 15:52 ` Noam Postavsky
2018-02-02 18:52 ` Drew Adams
2018-02-02 19:08 ` Noam Postavsky
2018-02-02 21:37 ` Drew Adams
2018-02-02 22:14 ` Ista Zahn
2018-02-02 22:35 ` Noam Postavsky
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=5074511f-b3b3-45aa-80b4-130be08f30ec@default \
--to=drew.adams@oracle.com \
--cc=30217@debbugs.gnu.org \
--cc=acm@muc.de \
/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.