emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 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 21:08:30 -0400	[thread overview]
Message-ID: <m28u0d59f5.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87oa99ebsc.fsf@nicolasgoaziou.fr>

I submitted a patch for this. I still am not sure I did it quite right.
Is there a page anywhere that outlines what to do?

e.g.

create a branch, make changes, how to make patches, and mail them etc...
or some other preferred method?

thanks,

Nicolas Goaziou writes:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> That sounds fine to me. Would you then use
>>
>> :lexical nil
>
> Sure. However, Babel uses "yes" and "no" as booleans so we also need to
> support these. nil and t are fine too, obviously.
>
> You would need to define a new defconst
> `org-babel-header-args:emacs-lisp' to specify allowed values
> for :lexical.
>
> Also, this should probably be documented somewehere.
>
>
> Regards,


--
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

  reply	other threads:[~2016-04-17  1:08 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
2016-04-16 16:52     ` Nicolas Goaziou
2016-04-17  1:08       ` John Kitchin [this message]
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=m28u0d59f5.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --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).