From: Max Nikulin <manikulin@gmail.com>
To: 52545@debbugs.gnu.org
Subject: bug#52545: 29.0.50; Make org-babel-execute-buffer ignore irrelevant src blocks
Date: Tue, 28 Dec 2021 18:45:39 +0700 [thread overview]
Message-ID: <b6d6d004-6c1a-7f5e-a114-4f068afb8e48@gmail.com> (raw)
In-Reply-To: <m2lf05686e.fsf@me.com>
On 28/12/2021 04:37, Rudolf Adamkovič wrote:
> Max Nikulin writes:
>
>> Let's consider the following example:
>>
>> ---- >8 ----
>> Test
>>
>> #+begin_src elisp
>> (message "Test")
>> #+end_src
>> ---- 8< -----
>>
>> emacs -Q -L ~/src/org-mode/lisp/ --eval "(custom-set-variables
>> '(org-babel-load-languages '((emacs-lisp . nil))))" babel-exec.org
>>
>> Do you agree that "No org-babel-execute function for elisp!" is a
>> reasonable reaction to `org-babel-execute-buffer`?
>
> The user did ask Org to load "emacs-lisp" but to never execute it.
> Thus, I would expect Org to do just that. What do you think?
No, it means instruction to unload support of emacs-lisp even it was
loaded before.
See info "(org) Languages" https://orgmode.org/manual/Languages.html and
`org-babel-do-load-languages' function. The latter may be considered too
technical for ordinary user, but examples of its usage are excessively
proliferated, e.g. it is mentioned for every supported language on Worg
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-octave.html
The function is called when the value of `org-babel-load-languages' is
changed through easy customization interface, so (emacs-lisp . nil) is a
command rather than a declaration.
The use case is to temporary enable support of some language and later
to disable it again without terminating of emacs session. Just to avoid
accidental execution of some snippet.
I can not say that your expectation of the effect of nil is a nonsense,
but changing its interpretation may cause silent failures and as a
result upset users. Consider that a file that includes source code
blocks for different languages is moved to another machine (or
configuration changed since previous execution on the same machine). It
is better to get explicit error than to copy result in a hurry and to
discover that it is incomplete some time later. Per-file and per-block
configuration is safer against such pitfalls.
I do not insist that current behavior is the best possible. There are
still some reasons behind such choice.
next prev parent reply other threads:[~2021-12-28 11:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2h7b8u9a7.fsf@me.com>
2021-12-17 4:51 ` bug#52545: 29.0.50; Make org-babel-execute-buffer ignore irrelevant src blocks Kyle Meyer
2021-12-17 19:25 ` Berry, Charles
2021-12-18 9:49 ` Ihor Radchenko
2021-12-18 19:57 ` Berry, Charles
2021-12-18 20:13 ` Berry, Charles
2021-12-21 22:53 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-21 23:14 ` Berry, Charles
2021-12-22 15:04 ` Ihor Radchenko
2021-12-23 22:00 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-24 4:09 ` Ihor Radchenko
2021-12-24 19:52 ` Berry, Charles
2021-12-25 21:37 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-25 23:34 ` Berry, Charles
2021-12-30 7:26 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-30 8:00 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-31 12:05 ` Max Nikulin
2021-12-31 19:11 ` Berry, Charles
2022-01-01 20:32 ` Rudolf Adamkovič via General discussions about Org-mode.
2022-01-01 20:23 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-30 20:14 ` Berry, Charles
2021-12-29 12:53 ` Max Nikulin
2021-12-29 17:47 ` Berry, Charles
2021-12-30 15:41 ` Max Nikulin
2021-12-25 21:40 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-26 12:49 ` Max Nikulin
2021-12-26 13:27 ` Ihor Radchenko
2022-01-04 14:59 ` Max Nikulin
2021-12-26 19:51 ` Rudolf Adamkovič
2021-12-27 11:18 ` Max Nikulin
2021-12-27 21:37 ` Rudolf Adamkovič via General discussions about Org-mode.
2021-12-28 11:45 ` Max Nikulin [this message]
2021-12-28 20:39 ` Rudolf Adamkovič via General discussions about Org-mode.
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=b6d6d004-6c1a-7f5e-a114-4f068afb8e48@gmail.com \
--to=manikulin@gmail.com \
--cc=52545@debbugs.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).