emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Kodi Arfer <listu@arfer.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How is the return value of `org-babel-execute:FOO` interpreted?
Date: Sun, 03 Oct 2021 21:09:34 +0800	[thread overview]
Message-ID: <87r1d2cl0x.fsf@localhost> (raw)
In-Reply-To: <e22b550b-a345-c894-7e2e-81c52c219827@arfer.net>

Kodi Arfer <listu@arfer.net> writes:

> It works, thank you. I should've looked at the changelog more closely. I wonder why this change was made. It would be annoyingly redundant to put `:results file` next to every `:file`. I already have code to change the default value of `:results` when `:file` is set, for a different Babel language, so I should be able to adapt that to this language.

There are tools like subtree-local headers args or default headers args
at your disposal.

The argument why that change was made is the following (commit 26ed66b23):

>> Deducing the results from some other arguments is not obvious.
>> Moreover, it prevents users from setting, e.g., :file-ext, in a node
>> property, as every block would then create a file.
>> 
>> Reported-by: Alex Fenton <alex@pressure.to>
>> <http://lists.gnu.org/r/emacs-orgmode/2018-05/msg00469.html>

Best,
Ihor


  reply	other threads:[~2021-10-03 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 16:43 How is the return value of `org-babel-execute:FOO` interpreted? Kodi Arfer
2021-10-03  9:38 ` Ihor Radchenko
2021-10-03 12:03   ` Kodi Arfer
2021-10-03 12:20     ` Ihor Radchenko
2021-10-03 12:39       ` Ihor Radchenko
2021-10-03 12:49         ` Kodi Arfer
2021-10-03 13:09           ` Ihor Radchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-02 13:27 Kodi Arfer

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=87r1d2cl0x.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=listu@arfer.net \
    /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).