Hi, Thank you for having a look.
Tim Cross writes:
This also seems like an edge case and I'm not convinced yet another option is justified. Why have eilisp in org blocks rather than an emacs-lisp block?
By org src blocks I meant an org emacs-lisp src block. The point of the patch is to be able to eval-defun some lisp code in an emacs-lisp src block from the org-buffer.
As this is a breaking change, it should not be on by default.
Currently eval-defun errors out, and fixing that will break things sooner or later, I think. I do not mind updating the patch to set the new option to nil by default, although I'll wait for a second opinion on this. Regards, -- Sébastien Miquel
