From: "Berry, Charles" <ccberry@health.ucsd.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Rudolf Adamkovič" <salutis@me.com>,
"Kyle Meyer" <kyle@kyleam.com>,
"52545@debbugs.gnu.org" <52545@debbugs.gnu.org>
Subject: bug#52545: 29.0.50; Make org-babel-execute-buffer ignore irrelevant src blocks
Date: Fri, 24 Dec 2021 19:52:38 +0000 [thread overview]
Message-ID: <840BA83C-A261-49FD-8FE5-EFEEA2DDEBCB@health.ucsd.edu> (raw)
In-Reply-To: <8735mitzij.fsf@localhost>
> On Dec 23, 2021, at 8:09 PM, Ihor Radchenko <yantar92@gmail.com> wrote:
>
> Rudolf Adamkovič <salutis@me.com> writes:
>
>>> So, Org cannot distinguish between language backends that are simply
>>> not loaded and the ones that do not define org-babel-execute:lang.
>>
>> Oh, if we have this architectural limitation in place, then Org cannot
>> help the user, and every user will have "explain" to Org that executing
>> BibTeX makes no sense. I guess we can then close this bug then!
>
> Not necessarily close. As I proposed above, one way is adding a user
> customisation. And we do not have to force the users adding trivial
> things like bibtex. Bibtex may be one of the defaults.
Honestly, I think there is no problem here to solve.
If there is a use case that you think I didn't cover below, please provide an ECM and directions for triggering the unwanted behavior.
Details:
---
Exports do not eval blocks for which there is no org-babel-execute:<lang>.
So, `C-c C-e l L' (and so on) will *not eval* bibtex src blocks.
The problem cited here *only* exists for execution using org-babel-execute-buffer or similar functions.
For that case, setting buffer or heading properties, such as:
#+begin_src org
:PROPERTIES:
:header-args: :eval yes :exports results
:header-args:bibtex: :eval no
:END:
#+end_src
resolves the issue.
So the user needs to add just one-line per language to set this up.
Following (info "(org) Property Syntax") the user can set this behavior for all Org files by customize-ing `org-global-properties', whose docstring gives plentiful details.
---
HTH,
Chuck
next prev parent reply other threads:[~2021-12-24 19:54 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 [this message]
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
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=840BA83C-A261-49FD-8FE5-EFEEA2DDEBCB@health.ucsd.edu \
--to=ccberry@health.ucsd.edu \
--cc=52545@debbugs.gnu.org \
--cc=kyle@kyleam.com \
--cc=salutis@me.com \
--cc=yantar92@gmail.com \
/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).