From: Noam Postavsky <npostavs@gmail.com>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: Richard Stallman <rms@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Improving aesthetics & readability of backquote
Date: Mon, 20 May 2019 22:22:37 -0400 [thread overview]
Message-ID: <CAM-tV-9S0C04OZjUOQmG16YtEhNn8hRGAFU=PO8iBXBaah_xkw@mail.gmail.com> (raw)
In-Reply-To: <m2woikmuhy.fsf@paulwrankin.com>
On Mon, 20 May 2019 at 22:06, Paul W. Rankin <hello@paulwrankin.com> wrote:
> On Tue, May 21 2019, Richard Stallman wrote:
>> Backquote is a well-known construct, a de-facto standard since over
>> 40 years ago.
> backquote may well be a 40-year-old standard,
The standard is about the read syntax; at least, Common Lisp
explicitly says it is implementation dependent what the result of
(read "`(foo ,bar)") is.
For Emacs, that currently gives (\` (foo (\, bar))), I think it would
be nicer if it gave (quasiquote (foo (unqote bar)). From what I can
tell this has been standard in Scheme since r3rs (1986).
next prev parent reply other threads:[~2019-05-21 2:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 3:03 Improving aesthetics & readability of backquote Paul W. Rankin
2019-05-20 3:38 ` Stefan Monnier
2019-05-22 15:44 ` Stefan Monnier
2019-05-20 8:52 ` Alan Mackenzie
2019-05-20 13:25 ` Paul W. Rankin
2019-05-20 14:02 ` Alan Mackenzie
2019-05-20 14:26 ` Paul W. Rankin
2019-05-20 16:08 ` Ken Olum
2019-05-20 23:19 ` Richard Stallman
2019-05-21 2:06 ` Paul W. Rankin
2019-05-21 2:22 ` Noam Postavsky [this message]
2019-05-21 2:39 ` Paul W. Rankin
2019-05-21 20:19 ` Richard Stallman
2019-05-22 2:46 ` Paul W. Rankin
2019-05-22 7:56 ` Eli Zaretskii
2019-05-22 8:55 ` Paul W. Rankin
2019-05-22 15:57 ` Michael Heerdegen
2019-05-22 16:13 ` 조성빈
2019-05-22 16:13 ` Michael Heerdegen
2019-05-22 22:40 ` Richard Stallman
2019-05-20 8:59 ` Lars Ingebrigtsen
2019-05-20 13:35 ` Paul W. Rankin
2019-05-20 13:47 ` Basil L. Contovounesios
2019-05-20 14:18 ` Paul W. Rankin
2019-05-20 14:48 ` Basil L. Contovounesios
2019-05-20 15:25 ` Lars Ingebrigtsen
2019-05-20 23:21 ` Richard Stallman
2019-05-21 2:34 ` Paul W. Rankin
2019-05-22 16:14 ` Sam Steingold
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='CAM-tV-9S0C04OZjUOQmG16YtEhNn8hRGAFU=PO8iBXBaah_xkw@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.com \
--cc=rms@gnu.org \
/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).