From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Alan Mackenzie <acm@muc.de>, 30217@debbugs.gnu.org
Subject: bug#30217: Ambiguity in NEWS in emacs-26.0.91
Date: Sun, 28 Jan 2018 10:52:18 -0500 [thread overview]
Message-ID: <87po5ukmkt.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87vafsm8e2.fsf@users.sourceforge.net> (Noam Postavsky's message of "Tue, 23 Jan 2018 19:02:13 -0500")
tags 30217 fixed
close 30217 27.1
quit
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> Anyway, thinking about this made realize I broke read->print
> round-tripping for these symbols, because I didn't change print to add
> the backslash. Attached is a patch which does this, but I'm not sure if
> it can go into emacs-26. If not, then I think we should at least delay
> introduction of the reader change to Emacs 27.
I've reverted the reader change from emacs-26 [1: 0510a78da5], and made
the printer change in master [2: 36c8128e74].
[1: 0510a78da5]: 2018-01-28 10:49:51 -0500
Revert "Signal error for symbol names with strange quotes (Bug#2967)"
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=0510a78da5faaa40ebfdf59d0ac6107a72c1be1d
[2: 36c8128e74]: 2018-01-28 10:43:01 -0500
Fix round tripping of read->print for symbols with strange quotes
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=36c8128e740ce91af10769bef46a21a72dafc56c
next prev parent reply other threads:[~2018-01-28 15:52 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
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 [this message]
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
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=87po5ukmkt.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=30217@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=drew.adams@oracle.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).