From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [TASK] Allow customizeable ditaa executable in ob-ditaa.el
Date: Fri, 10 Nov 2023 17:38:19 +0700 [thread overview]
Message-ID: <uil16s$6no$1@ciao.gmane.io> (raw)
In-Reply-To: <87zfzmnvl7.fsf@t14.reltub.ca>
On 10/11/2023 10:19, Leo Butler wrote:
> On Thu, Nov 09 2023, Max Nikulin wrote:
>
>> diff --git a/lisp/ob-ditaa.el b/lisp/ob-ditaa.el
[...]
>> should allow to set :java to
>>
>> flatpak-spawn --host toolbox run /usr/bin/ditaa
>>
>> without abusing of org-ditaa-jar-path. Untested.
>
> Doesn't this abuse the `java' header argument, which is intended to pass
> arguments to the java runtime?
or `org-babel-ditaa-java-cmd'. My point is that requirement of non-empty
`org-ditaa-jar-path' confused Florin to the degree when workarounds
looked impossible. Notice that setting
org-ditaa-jar-path "/usr/bin/ditaa"
still requires spreading of "flatpack-spawn ..." over
`org-babel-ditaa-java-cmd', :java, and `org-ditaa-jar-option'.
fortunately some of these options may be sent empty and other will not
quote spaces, etc. Whole "flatpack-spawn ... ditaa" command can not be
put to `org-ditaa-jar-path'
> I think that it would be best to implement the change to mirror that
> done in ob-plantuml, as Ihor suggested earlier.
Agree. I appreciate consistency in treatment of similar cases.
I am not sure in the following idea. Perhaps a concept of "launcher" (or
"runner") may be introduced. Launchers may be stacked. So for a jar file
launcher is "java @:java -jar" that may be combined with "toolbox run"
and "flatpak-spawn --host" launchers.
> My reading of the documentation and ob-plantuml.el is that it is not
> possible to use the `java' header argument in the way you propose for
> ob-ditaa.el.
Since nobody has proposed a patch for ob-ditaa, I decided that making a
workaround easier is an improvement.
#+property: header-args:ditaa :java ...
would not affect ob-plantuml.
P.S. I am unsure what is proper balance between flexibility/convenience
and security. A file downloaded from net should not be able to change
executables and their options without consent from the user.
Unfortunately attempts to suppress at least shell expansion will lead to
more verbose configuration.
next prev parent reply other threads:[~2023-11-10 10:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 10:59 org-ditaa woes Florin Boariu
2023-10-20 17:22 ` Leo Butler
2023-10-20 18:16 ` Dr. Arne Babenhauserheide
2023-10-20 19:31 ` Leo Butler
2023-10-20 21:39 ` Florin Boariu
2023-10-21 3:50 ` Max Nikulin
2023-10-23 11:18 ` Florin Boariu
2023-10-24 7:55 ` Max Nikulin
2023-10-24 9:31 ` Florin Boariu
2023-10-24 9:38 ` Ihor Radchenko
2023-10-25 19:00 ` Leo Butler
2023-10-26 8:44 ` Max Nikulin
2023-10-26 9:30 ` Ihor Radchenko
2023-12-20 18:03 ` Leo Butler
2023-12-21 14:15 ` Ihor Radchenko
2023-10-26 15:32 ` Leo Butler
2023-10-23 12:25 ` Florin Boariu
2023-10-21 7:44 ` Dr. Arne Babenhauserheide
2023-10-21 8:56 ` [TASK] Allow customizeable ditaa executable in ob-ditaa.el (was: org-ditaa woes) Ihor Radchenko
2023-11-09 3:17 ` [TASK] Allow customizeable ditaa executable in ob-ditaa.el Leo Butler
2023-11-09 12:17 ` Max Nikulin
2023-11-10 3:19 ` Leo Butler
2023-11-10 10:09 ` Ihor Radchenko
2023-11-10 10:38 ` Max Nikulin [this message]
2023-11-10 15:21 ` Leo Butler
2023-11-11 10:07 ` Ihor Radchenko
2023-11-10 10:18 ` Ihor Radchenko
2023-11-10 14:59 ` Leo Butler
2023-11-11 10:24 ` Ihor Radchenko
2023-11-13 16:26 ` Leo Butler
2023-11-15 11:12 ` Formatting worg code examples (was: Re: [TASK] Allow customizeable ditaa executable in ob-ditaa.el) Max Nikulin
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='uil16s$6no$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).