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: Sun, 07 Jan 2018 13:21:36 +0000 [thread overview]
Message-ID: <CAArVCkRUha_J9aUf_LK5sV2Eg=dzeTqbE568JOF+MF5+WqJ9RA@mail.gmail.com> (raw)
In-Reply-To: <625f0892-0eaf-4ab6-2abd-50363c8c7a49@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am So., 31. Dez. 2017 um 01:40 Uhr:
> Philipp Stephani wrote:
> >
> > Only in Emacs 28, because 26 will still have old-style backquotes only.
>
> Ah, OK, I was turned around then: this variable is for
> forward-compatibility and
> not backward. I suggest mentioning in the doc string that setting the
> variable
> makes Emacs compatible with planned-for-28 behavior, and that the variable
> is
> planned to go away in Emacs 28. (It's a temporary variable, so to
> speak....)
>
Good point, I've amended the docstring and pushed the patch to master as
ddb74b2027.
[-- Attachment #2: Type: text/html, Size: 903 bytes --]
next prev parent reply other threads:[~2018-01-07 13:21 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
2017-12-31 0:40 ` Paul Eggert
2018-01-07 13:21 ` Philipp Stephani [this message]
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='CAArVCkRUha_J9aUf_LK5sV2Eg=dzeTqbE568JOF+MF5+WqJ9RA@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).