emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] oddity tangling src_blk with :var [9.7-pre (release_9.6.26-1368-g1ae978 @ /home/minshall/.emacs.d/straight/build/org/)]
Date: Mon, 29 Apr 2024 12:48:39 +0000	[thread overview]
Message-ID: <87cyq8cp20.fsf@localhost> (raw)
In-Reply-To: <182617.1714330440@archlinux>

Greg Minshall <minshall@umich.edu> writes:

>> This is because Org mode currently cannot distinguish between babel
>> backends that simply do not support variable assignments and babel
>> backends that are not loaded.
>
> currently, is it possible to see well enough what is going on to
> generate an error and abort the tangle?
>
> (off the top of my head i would think a `:var` in either of the
> situations you describe might be described as an error -- albeit a user
> error.)

Not necessarily.

Consider something like


#+property: header-args :var common_variable = "foo"

#+begin_src elisp
(message "variable is %S" common_variable)
#+end_src

#+RESULTS:
: variable is "foo"

#+begin_src python :result value
return f"variable is \"{common_variable}\""
#+end_src

#+RESULTS:
: variable is "foo"

Below, ob-dot does not implement variable assignments.
Throwing an error here would be unexpected.

#+begin_src dot :file foo.png
digraph G {
a -> b
}
#+end_src

#+RESULTS:
[[attachment:foo.png]]

We may, theoretically, only throw an error when the variable assignments
are not inherited, but that will create even more confusion - sometimes,
the error will be thrown, and sometimes not.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-04-29 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 10:05 [BUG] oddity tangling src_blk with :var [9.7-pre (release_9.6.26-1368-g1ae978 @ /home/minshall/.emacs.d/straight/build/org/)] Greg Minshall
2024-04-28 12:29 ` Ihor Radchenko
2024-04-28 18:54   ` Greg Minshall
2024-04-29 12:48     ` Ihor Radchenko [this message]
2024-04-30  7:38       ` Greg Minshall
2024-04-30 10:33         ` Ihor Radchenko
2024-05-01 17:41           ` Greg Minshall
2024-05-01 17:47             ` Ihor Radchenko
2024-05-02 13:01               ` Greg Minshall

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=87cyq8cp20.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \
    /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).