From: John Kitchin <jkitchin@andrew.cmu.edu>
To: John Kitchin <jkitchin@andrew.cmu.edu>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: funny emacs-lisp macro behavior in org-babel related to lexical-binding
Date: Sat, 16 Apr 2016 09:41:45 -0400 [thread overview]
Message-ID: <CAJ51ETqmS5gF-NQuNd1tiLAH6pwEs3CaaFrEv16P0ftA0vRc0A@mail.gmail.com> (raw)
In-Reply-To: <87wpnysikp.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
That sounds fine to me. Would you then use
:lexical nil
in a header to turn it off? or a new custom variable?
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Fri, Apr 15, 2016 at 4:49 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > So, I would like to propose adding the third argument to the eval
> > statement that reads
> >
> > (assoc :lexical params)
> >
> > to turn on lexical eval if you want it.
> >
> > What do you think?
>
> I assume you're talking about ob-emacs-lisp.el. This sounds like a good
> idea. However, I suggest to make lexical binding the default value, to
> be on par with the rest of Emacs.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1727 bytes --]
next prev parent reply other threads:[~2016-04-16 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 18:36 funny emacs-lisp macro behavior in org-babel related to lexical-binding John Kitchin
2016-04-15 20:49 ` Nicolas Goaziou
2016-04-16 13:41 ` John Kitchin [this message]
2016-04-16 16:52 ` Nicolas Goaziou
2016-04-17 1:08 ` John Kitchin
2016-04-17 8:18 ` Thomas S. Dye
2016-04-17 16:11 ` Charles C. Berry
2016-04-17 23:03 ` John Kitchin
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=CAJ51ETqmS5gF-NQuNd1tiLAH6pwEs3CaaFrEv16P0ftA0vRc0A@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@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/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).