From: Andrea Corallo <akrl@sdf.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Kangas <stefan@marxist.se>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: "Bringing GNU Emacs to Native Code" at the European Lisp Symposium
Date: Wed, 29 Apr 2020 18:57:51 +0000 [thread overview]
Message-ID: <xjfblna2k7k.fsf@sdf.org> (raw)
In-Reply-To: <cf81ab51-258f-4866-b985-3fa1c2fed3a8@default> (Drew Adams's message of "Wed, 29 Apr 2020 08:35:23 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> As the reference in the previous phrase explains
>> this is just about what we control in Emacs with
>> the `lexical-binding' variable.
>
> Dunno what previous phrase you refer to. That
> variable isn't mentioned in the paper (other
> than appearing in a code example).
>
> A suggestion would be to be explicit about this
> in the future - or else explain the phrase.
I was referring to the phrase just before the one we are discussing:
"We point out that, since Emacs Lisp received in 2012 lexical scope
support, two different sub-languages are currently coexisting [15,
Sec. 8.1]."
> I personally think the phrase used is confusing,
> and perhaps misleading. Yes, one could argue
> that variable `lexical-binding' kind of splits
> Elisp currently into two languages. But that's
> not a usual way of looking at it, and it's not
> the way that Emacs talks about itself.
I agree with you that could have been stated more clearly without
assuming the user had visited the reference (this is not a correct
assumption).
>
>> Apologies if you think this could have been
>> phrased better, I hope the misunderstanding
>> is clarified.
>
> No need to apologize, at all. It's clear to me
> now; thank you for clarifying.
>
> And thanks for the great work (!) and clear
> paper about it.
Thanks again.
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-04-29 18:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 17:11 "Bringing GNU Emacs to Native Code" at the European Lisp Symposium Stefan Kangas
2020-04-28 19:25 ` Andrea Corallo
2020-04-28 19:35 ` Amin Bandali
2020-04-28 20:06 ` Andrea Corallo
2020-04-28 21:13 ` Amin Bandali
2020-04-29 3:24 ` Richard Stallman
2020-04-29 18:47 ` Andrea Corallo
2020-04-28 19:36 ` tomas
2020-04-28 22:00 ` Drew Adams
2020-04-28 22:18 ` Stefan Monnier
2020-04-28 22:51 ` Drew Adams
2020-04-29 7:04 ` Eli Zaretskii
2020-04-29 12:38 ` Stefan Monnier
2020-04-29 14:02 ` Eli Zaretskii
2020-04-28 22:38 ` Dmitry Gutov
2020-04-29 10:55 ` Andrea Corallo
2020-04-29 15:35 ` Drew Adams
2020-04-29 18:57 ` Andrea Corallo [this message]
2020-04-29 19:29 ` Drew Adams
2020-04-30 1:14 ` Stefan Monnier
2020-04-30 2:27 ` Richard Stallman
2020-04-30 3:00 ` Stefan Monnier
2020-05-02 2:21 ` Richard Stallman
2020-05-02 13:43 ` Stefan Monnier
2020-04-30 20:32 ` Andrea Corallo
2020-05-02 2:27 ` Richard Stallman
2020-05-02 9:48 ` Andrea Corallo
2020-05-03 3:44 ` Richard Stallman
2020-05-03 4:28 ` Stefan Monnier
2020-05-04 3:09 ` Richard Stallman
2020-05-04 5:17 ` Stefan Monnier
2020-05-05 2:56 ` Richard Stallman
2020-05-05 3:18 ` Stefan Monnier
2020-05-04 10:07 ` Andrea Corallo
2020-05-02 13:50 ` 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=xjfblna2k7k.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).