Gerard Vermeulen writes:
>> (setq org-babel-default-header-args:text '((:eval . "no")))
>>
>> to your config.
>
> Is it possible to make org-lint recognize those settings?
>
> I have the kludge
>
> (defun org-babel-execute:text (_body _params)
>"NO-OP to silence warnings." nil)
>
> in my
On 16.03.2024 12:48, Ihor Radchenko wrote:
Yes. You can add
#+property: header-args:text :eval no
on top of your Org file or add
(setq org-babel-default-header-args:text '((:eval . "no")))
to your config.
Is it possible to make org-lint recognize those settings?
I have the kludge
Ihor Radchenko writes:
> Yes. You can add
> #+property: header-args:text :eval no
> on top of your Org file or add
> (setq org-babel-default-header-args:text '((:eval . "no")))
> to your config.
org is amazing!
Thank you very much for all your work.
--
Damien Cassou
"Success is the ability
Damien Cassou writes:
> If I understand correctly, you are saying that it is better to let the
> command crash as soon as possible instead of letting it execute
> potentially problematic code because some previous block has not been
> executed. I think it makes perfect sense. I'm now convinced
Hi Ihor,
Ihor Radchenko writes:
> For example, consider
>
> #+begin_src bash
> mkdir foo
> #+end_src
>
> #+begin_src emacs-lisp
> (write-file "foo/result")
> #+end_src
>
> The second block relies upon side effects of the first block.
> However, if ob-shell is not loaded, with your patch, the
Damien Cassou writes:
> Ihor Radchenko writes:
>> Thanks for the patch, but it is not obvious that skipping src blocks
>> that cannot be executed is always a good idea. Consider, for example,
>> that some blocks are used as input for other blocks. Then, failing to
>> execute them means that
Hi Ihor,
Ihor Radchenko writes:
> Thanks for the patch, but it is not obvious that skipping src blocks
> that cannot be executed is always a good idea. Consider, for example,
> that some blocks are used as input for other blocks. Then, failing to
> execute them means that other blocks may have
Damien Cassou writes:
> The command `org-babel-execute-buffer' tries to execute all source code
> blocks of the current buffer. When it encounters a block that is not
> executable the command crashes. The attached patch makes the command ignore
> non-executable blocks and move on.
> ...
> -
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
