From: Tim Cross <theophilusx@gmail.com>
To: TEC <tecosaur@gmail.com>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, emacs-orgmode@gnu.org
Subject: Re: The fate of ditaa.jar (9.4.5.)
Date: Wed, 12 May 2021 10:06:47 +1000 [thread overview]
Message-ID: <87fsysbwyo.fsf@gmail.com> (raw)
In-Reply-To: <87v97ph1p9.fsf@gmail.com>
TEC <tecosaur@gmail.com> writes:
> Tim Cross <theophilusx@gmail.com> writes:
>
>> I also had to install textlive, plantuml, graphviz, taskjuggler,
>> ledger, sqlite and many other things.
>
> Perhaps it would be good to make a table of
>
> | software | needed for | package name | download page |
>
> and/or prompt users when an action requiring another executable is
> undertaken if it isn't found.
Useful additional documentation, assuming it can be maintained, is
rarely a bad idea. A table on worg (with maybe a link in the manual)
which lists all the org (and contrib) features, external dependencies
and link to canonical source would probably be a good idea.
I find it hard to remember how I worked out all the dependencies as I
adopted org as it was so long ago and I was already a heavy user of
many of the tools/dependencies of org. This makes it challenging to
appreciate how hard it can be for someone knew to org. On the other
hand, if we make it overly easy/automatic, we run the risk of
disempowering the user and making them more dependent on assistance from
others. Finding the right balance between informative and concise is a
challenge. If we provide too much information, it can be overwhelming,
too little and it can be confusing. I find it harder to write good
documentation than good code!
--
Tim Cross
next prev parent reply other threads:[~2021-05-12 0:49 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
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 [this message]
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=87fsysbwyo.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
/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).