From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bruno Barbier <brubar.cs@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-babel guile source block bug in handling multiple values
Date: Fri, 10 Mar 2023 10:42:17 +0000 [thread overview]
Message-ID: <46e6f579-9eca-e1da-06ea-f2478a603c5a@posteo.de> (raw)
In-Reply-To: <87sfeeoysf.fsf@localhost>
On 3/9/23 14:10, Ihor Radchenko wrote:
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>
>> ~~~~START~~~~
>> #+name: python-imports
>> #+begin_src python :python /usr/bin/python3 :results output replace drawer :var x=4
>> import math
>>
>> y = math.sqrt(x)
>> # print(y)
>> #+end_src
>>
>> #+name: python-usage
>> #+begin_src python :python /usr/bin/python3 :return :noweb strip-export :results value replace drawer
>> <<python-imports>>
>>
>> print("y: {}".format(y))
>> #+end_src
>> ~~~~~END~~~~~
>>
>> Unfortunately, this example does not seem to work at all, but for a different
>> reason:
>>
>> It seems that using any Python source block with :var header args via :noweb
>> does not work, as it then behaves in the way, that it merely pasted the included
>> source block, without first putting in the :var values into the variables. I get
>> errors about those :var variables being undefined, of course, since they are on
>> the included source block, not on the including one:
>>
>> ~~~~START: *Org-Babel Error Output*~~~~
>> Traceback (most recent call last):
>> File "<stdin>", line 10, in <module>
>> File "<stdin>", line 5, in main
>> NameError: name 'x' is not defined
>> [ Babel evaluation exited with code 1 ]
>> ~~~~~END~~~~~
> This is expected. Noweb includes the src block code without altering it.
> See 16.11 Noweb Reference Syntax
>
> We may probably clarify this in the manual. Would it be helpful?
I think it would be helpful. I merely tried Python, because it was at hand and
because I did not find ob-racket in M-x package-list RET and did not have
another Scheme installed. Cannot say, whether others find the behavior confusing
or not, but I imagine I would find it helpful, if it was mentioned in the docs.
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2023-03-10 10:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 11:27 org-babel guile source block bug in handling multiple values Zelphir Kaltstahl
2023-03-07 14:36 ` Ihor Radchenko
2023-03-07 15:18 ` Zelphir Kaltstahl
2023-03-07 19:52 ` Bruno Barbier
2023-03-08 0:55 ` Zelphir Kaltstahl
2023-03-08 19:38 ` Bruno Barbier
2023-03-09 0:44 ` Zelphir Kaltstahl
2023-03-09 13:04 ` [BUG] Inconsistent global/local :var assignments in ob-* for lisps and non-lisps (was: org-babel guile source block bug in handling multiple values) Ihor Radchenko
2023-03-10 10:39 ` Zelphir Kaltstahl
2023-03-11 9:58 ` Ihor Radchenko
2023-03-11 18:30 ` Zelphir Kaltstahl
2023-03-12 11:33 ` Ihor Radchenko
2023-03-19 13:50 ` [PATCH] lisp/ob-scheme.el Zelphir Kaltstahl
2023-03-22 10:43 ` Ihor Radchenko
2023-03-25 14:34 ` Zelphir Kaltstahl
2023-03-26 9:32 ` Ihor Radchenko
2023-04-25 12:28 ` Ihor Radchenko
2023-04-29 11:08 ` Zelphir Kaltstahl
2023-03-09 13:10 ` org-babel guile source block bug in handling multiple values Ihor Radchenko
2023-03-10 10:42 ` Zelphir Kaltstahl [this message]
2023-03-11 10:18 ` Ihor Radchenko
2023-06-02 13:11 ` Ihor Radchenko
2023-03-09 13:11 ` Ihor Radchenko
2023-03-09 14:21 ` Daniel Kraus
2023-03-10 11:57 ` Ihor Radchenko
2023-03-10 10:45 ` Zelphir Kaltstahl
2023-03-08 1:13 ` Zelphir Kaltstahl
2023-03-08 8:55 ` Ihor Radchenko
2023-03-07 15:44 ` Max Nikulin
2023-03-07 21:41 ` Rudolf Adamkovič
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=46e6f579-9eca-e1da-06ea-f2478a603c5a@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=brubar.cs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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).