From: Arthur Miller <arthur.miller@live.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: The fate of ditaa.jar (9.4.5.)
Date: Thu, 13 May 2021 16:06:56 +0200 [thread overview]
Message-ID: <AM9PR09MB4977A7015BB6A9DB9C24C86696519@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <87zgwy952d.fsf@iki.fi> (Jarmo Hurri's message of "Thu, 13 May 2021 15:44:10 +0300")
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> Greetings.
>
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>
>> Arthur Miller <arthur.miller@live.com> writes:
>>
>>> By the way, how difficult is to download one file from the internet
>>> (ditaa.jar) if you are an user?
>>
>> That’s not the point. The point is that every single user with a ditaa
>> block has to do it.
>>
>> Ask the other way round: What is the benefit of removing ditaa from
>> org? If you want to force most current org-ditaa users to unbreak
>> their setup after update, there should be a significant tangible
>> benefit.
>
> I agree.
>
> One thing I like about org is that most things work out of the box.
If bundled ditaa is not compatible with jre installed on users
computer, or there is no jre installed, and user is not a programmer or
used to Java, how many steps it adds to such a user to sort out why org
does not work for him/her "out of the box"? Just to save some experienced
user an extra step, that probably does not even affect them since they
already have java and ditaa on their computers.
> Comparing ditaa to latex/java/C/such does not feel fair, since distros
Ditaa requires jre to work. Should org distribute a version of jre too
to make it sure it works on user computer "out of the box"?
next prev parent reply other threads:[~2021-05-13 14:22 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
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 [this message]
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=AM9PR09MB4977A7015BB6A9DB9C24C86696519@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
/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).