From: Bastien Guerry <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Add ob-sclang.el for sclang Org-mode babel support in contrib/
Date: Sun, 18 Jun 2017 23:32:03 +0200 [thread overview]
Message-ID: <87bmplrnho.fsf@bzg.fr> (raw)
In-Reply-To: <87a855c9ru.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 18 Jun 2017 22:37:25 +0200")
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> There is absolutely no drawback in using lexical binding. Since Emacs
> 24.1, it _is_ the default for Elisp: every Elisp file created activates
> it, the other binding being for compatibility with older libraries.
Maybe I miss something: when I create a file with C-x C-f whatever.el RET
it does not use a template or does not get created with lexical binding on.
What are you referring to when you say "every Elisp file created activates it"?
> Please, pretty please, don't suggest it is different.
Quoting the Emacs Lisp manual:
This is the ‘GNU Emacs Lisp Reference Manual’ corresponding to Emacs
version 26.0.50.
...
Scoping Rules for Variable Bindings
* Dynamic Binding:: The default for binding local variables in Emacs.
* Dynamic Binding Tips:: Avoiding problems with dynamic binding.
* Lexical Binding:: A different type of local variable binding.
...
12.10.1 Dynamic Binding
-----------------------
By default, the local variable bindings made by Emacs are dynamic
bindings. When a variable is dynamically bound, its current binding at
any point in the execution of the Lisp program is simply the most
recently-created dynamic local binding for that symbol, or the global
binding if there is no such local binding.
To me the manual clearly says dynamic binding is the default, and
that's why using lexical binding requires additional info in the file.
Whether lexical binding is a good default or not is another question,
and whether lexical-binding:t makes sense in a file with no binding
yet another, third one.
--
Bastien
next prev parent reply other threads:[~2017-06-18 21:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 0:43 Add ob-sclang.el for sclang Org-mode babel support in contrib/ numbchild
2017-06-10 8:17 ` Nicolas Goaziou
2017-06-11 2:02 ` numbchild
2017-06-14 14:02 ` Nicolas Goaziou
2017-06-15 6:21 ` Bastien Guerry
2017-06-15 7:53 ` numbchild
2017-06-15 7:56 ` numbchild
2017-06-15 8:26 ` Bastien Guerry
2017-06-15 11:19 ` numbchild
2017-06-15 11:14 ` numbchild
2017-06-15 12:38 ` Bastien Guerry
2017-06-16 23:25 ` numbchild
2017-06-17 10:53 ` Bastien Guerry
2017-06-17 12:23 ` numbchild
2017-06-17 12:46 ` Bastien Guerry
2017-06-17 13:14 ` numbchild
2017-06-17 14:27 ` Nicolas Goaziou
2017-06-18 8:34 ` Bastien Guerry
2017-06-18 9:31 ` Nicolas Goaziou
2017-06-18 19:45 ` Bastien Guerry
2017-06-18 20:37 ` Nicolas Goaziou
2017-06-18 21:32 ` Bastien Guerry [this message]
2017-06-19 9:20 ` Nicolas Goaziou
2017-06-19 10:14 ` Kaushal Modi
2017-06-19 10:37 ` Bastien Guerry
2017-06-19 14:44 ` numbchild
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmplrnho.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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/org-mode.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).