From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Philipp Stephani <phst@google.com>, emacs-devel@gnu.org
Subject: Re: [PATCH 1/2] Add new variable to force new-style backquote interpretation.
Date: Sat, 30 Dec 2017 23:29:40 +0000 [thread overview]
Message-ID: <CAArVCkQWunyzh2mE1KGjMV-1oSsvMk_Wqszh-bvS3-QvZZayLg@mail.gmail.com> (raw)
In-Reply-To: <bbda20da-dfac-9793-885e-4046bcf0b086@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am So., 31. Dez. 2017 um 00:07 Uhr:
> Philipp Stephani wrote:
> > As discussed in
> > http://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00051.html, we
> > (mostly) agreed to first turn them into errors
>
> And we've done that in Emacs 26, right?
No, only in master (i.e. Emacs 27), see
http://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00056.html
> So in Emacs 27 we can remove support for
> old-style backquotes;
Only in Emacs 28, because 26 will still have old-style backquotes only.
> we don't need a new variable to enable old-style
> backquotes dynamically.
>
My patch conditionally enables new-style backquotes; there's no way to
re-enable old-style backquotes once they generate errors. The assumption is
that everyone should migrate to new-style once they get the errors, and not
re-enable old-style.
[-- Attachment #2: Type: text/html, Size: 1679 bytes --]
next prev parent reply other threads:[~2017-12-30 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAArVCkRj3AhF0EDaSKu7a4zu1rYOx8Ac7+Hhj6gcC3sJQRGLtg@mail.gmail.com>
2017-12-29 20:59 ` [PATCH 1/2] Add new variable to force new-style backquote interpretation Philipp Stephani
2017-12-29 20:59 ` [PATCH 2/2] Improve error message for old-style backquotes Philipp Stephani
2017-12-30 6:19 ` [PATCH 1/2] Add new variable to force new-style backquote interpretation Paul Eggert
2017-12-30 9:02 ` Philipp Stephani
2017-12-30 23:07 ` Paul Eggert
2017-12-30 23:29 ` Philipp Stephani [this message]
2017-12-31 0:40 ` Paul Eggert
2018-01-07 13:21 ` Philipp Stephani
2017-12-31 5:08 ` Stefan Monnier
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=CAArVCkQWunyzh2mE1KGjMV-1oSsvMk_Wqszh-bvS3-QvZZayLg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=phst@google.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).