Ihor Radchenko writes:
> Applied onto main.
Thanks
> Have you seen org-babel-temp-stable-file?
I have not. Seems really useful, thanks for mentioning. I wrote my functions
before org-babel-temp-stable-file was added, but seems I can simplify them now
quite a bit.
I noticed two possible bugs
Ferdinand Pieper writes:
>> Have you seen org-babel-temp-stable-file?
>
> I have not. Seems really useful, thanks for mentioning. I wrote my functions
> before org-babel-temp-stable-file was added, but seems I can simplify them
> now quite a bit.
>
> I noticed two possible bugs in org-babel-tem
Ferdinand Pieper writes:
> Ihor Radchenko writes:
>
>> I'd prefer to change LIGHT to NO-EVAL, including in
>> org-babel-get-src-block-info. Changing argument name in function does
>> not affect its caller in any way. Just need to update the function body
>> and docstring carefully.
>>
>> NO-EVAL
Ihor Radchenko writes:
> I'd prefer to change LIGHT to NO-EVAL, including in
> org-babel-get-src-block-info. Changing argument name in function does
> not affect its caller in any way. Just need to update the function body
> and docstring carefully.
>
> NO-EVAL is already used by org-babel-parse-
Ferdinand Pieper writes:
> Similar to ~org-babel-get-src-block-info~ it is sometimes useful to disable
> evaluation of lisp parameters when getting the info of a lob call. This patch
> adds an argument for that.
>
> Better name for the argument could be ~no-eval~, but I decided to stick with
>
Similar to ~org-babel-get-src-block-info~ it is sometimes useful to disable
evaluation of lisp parameters when getting the info of a lob call. This patch
adds an argument for that.
Better name for the argument could be ~no-eval~, but I decided to stick with
the naming in ~org-babel-get-src-bloc
