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 20:39:37 +0800 [thread overview]
Message-ID: <87v92ecmeu.fsf@localhost> (raw)
In-Reply-To: <871r52e1v9.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> Kodi Arfer <listu@arfer.net> writes:
>
>>> Are you sure that you have :file parameter in the source block you tried
>>> to execute?
>>
>> Yes, this is my code block:
>>
>> #+begin_src hy :file g/foo.png
>> (plt.scatter [1 2 3] [4 5 -9])
>> #+end_src
>
> What about
>
> #+begin_src hy :results file :file g/foo.png
> (plt.scatter [1 2 3] [4 5 -9])
> #+end_src
>
> ?
If this code works for you, the problem is the folloing incompatible
change in Org 9.3 (see etc/ORG-NEWS file in the repo):
* Version 9.3
** Incompatible changes
*** ~:file~ header argument no longer assume "file" ~:results~
The "file" ~:results~ value is now mandatory for a code block
returning a link to a file. The ~:file~ or ~:file-ext~ header
arguments no longer imply a "file" result is expected.
Best,
Ihor
next prev parent reply other threads:[~2021-10-03 12:39 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 [this message]
2021-10-03 12:49 ` Kodi Arfer
2021-10-03 13:09 ` Ihor Radchenko
-- 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=87v92ecmeu.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).