From: Arthur Miller <arthur.miller@live.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: The fate of ditaa.jar (9.4.5.)
Date: Mon, 10 May 2021 22:49:30 +0200 [thread overview]
Message-ID: <AM9PR09MB4977A59A75B12CDE5F2CAF5E96549@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <87mtt2jz4h.fsf@web.de> (Arne Babenhauserheide's message of "Mon, 10 May 2021 19:07:58 +0200")
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
>
>> On Mon, May 10, 2021 at 02:28:57PM +0300, Jarmo Hurri wrote:
>>> I pulled the latest master and noticed that contrib has been moved into
>>> a separate repository. I also cloned this contrib repository, but can
>>> not find the file
>>>
>>> scripts/ditaa.jar
>>>
>>> in the repo. In fact, there is no directory scripts in the repo.
>>
>> I actually never considered this might be packaged with Org. I always
>> thought I had to install it separately, like my Latex distribution or
>> PlantUML.
>
> Bundling this makes ditaa code blocks just work. Otherwise they won’t
> work on every org-install.
The user still needs a Java runtime installed on his/her compute, so
bundling ditaa.jar gives no guarantee at all that ditaa blocks will just
work on every org-install.
Instead a less informaed user, not used to run java programs, might be
left with a not working application that fails silently or to the user
incomprehensible error message.
Better to point user to ditaa's sources/releases and inform it is
optional with org. That way non-informed user will have to install java
and ditaa and will at least have an idea where to look when things go wrong.
next prev parent reply other threads:[~2021-05-10 21:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 11:28 The fate of ditaa.jar (9.4.5.) Jarmo Hurri
2021-05-10 11:50 ` Eric S Fraga
2021-05-10 12:28 ` Russell Adams
2021-05-10 17:07 ` Dr. Arne Babenhauserheide
2021-05-10 20:49 ` Arthur Miller [this message]
2021-05-11 1:22 ` Christopher Dimech
2021-05-11 18:56 ` Arthur Miller
2021-05-11 20:53 ` Dr. Arne Babenhauserheide
2021-05-12 8:44 ` Arthur Miller
2021-05-12 9:41 ` Dr. Arne Babenhauserheide
2021-05-12 14:51 ` Russell Adams
2021-05-13 12:44 ` Jarmo Hurri
2021-05-13 14:06 ` Arthur Miller
2021-05-13 20:08 ` Dr. Arne Babenhauserheide
2021-05-14 1:13 ` Arthur Miller
2021-05-14 5:30 ` Dr. Arne Babenhauserheide
2021-05-14 5:39 ` Christopher Dimech
2021-05-14 11:23 ` Arthur Miller
2021-05-14 11:57 ` Christopher Dimech
2021-05-10 18:41 ` Nick Dokos
2021-05-11 1:25 ` Christopher Dimech
2021-05-11 4:33 ` Tim Cross
2021-05-11 6:35 ` Dr. Arne Babenhauserheide
2021-05-11 6:53 ` he " Christopher Dimech
2021-05-11 8:36 ` The " Tim Cross
2021-05-11 12:52 ` TEC
2021-05-11 19:15 ` Arthur Miller
2021-05-12 0:06 ` Tim Cross
2021-05-12 8:47 ` Arthur Miller
2021-05-15 17:31 ` [External] : " Daniel Ortmann
2021-05-11 19:02 ` Arthur Miller
2021-05-16 12:19 ` Bastien
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=AM9PR09MB4977A59A75B12CDE5F2CAF5E96549@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=arne_bab@web.de \
--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).