From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Volunteering to maintain ob-asymptote.el within Org
Date: Fri, 22 Jul 2022 10:28:24 +0300 [thread overview]
Message-ID: <87tu791u93.fsf@iki.fi> (raw)
In-Reply-To: 86h73avk7w.fsf@bonfacemunyoki.com
Greetings Munyoki.
Munyoki Kilyungi <me@bonfacemunyoki.com> writes:
> Hi Jarmo!
>
> Jarmo Hurri <jarmo.hurri@iki.fi> anaandika:
>
>> I hereby volunteer to maintain ob-asymptote.el.
>
> Nice!
>
>> This file has been moved
>> to org-contrib, but I would like it to be brought back into Org itself.
>>
>> I strongly feel that Asymptote is way too valuable as a scientific tool
>> to be dropped out of Org.
> Isn't this debatable?
Yes, that is a good reason to be involved in these discussions.
> TBH, this is the first time I'm hearing about it. I've looked it up,
> and indeed it seems to be useful.
For some reason, even people who would certainly benefit from Asymptote
often have not heard of it. The developers do not really
advertise. Asymptote is amazingly powerful and sophisticated.
> That said, shouldn't this be in org-contrib? Too many features in a
> tool - featurism - may be distracting, in the sense that you focus
> more on your tool than work at hand.
I do not understand this. Why would supporting a professional-level
graphics programming language be distracting someone from their work
when using Org?
> And that said, to work around this, I reckon that's why (?) we have
> org-contrib. You - the end user - install what you want/need.
Yes, but whenever we split up support, we raise the threshold for the
use of a combination of tools, in this case Org and Asymptote.
Org is a very powerful publication tool. Does it not make complete sense
to include support for a tool for creating professional-quality
publication graphics?
All the best,
Jarmo
next prev parent reply other threads:[~2022-07-22 7:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 5:16 Volunteering to maintain ob-asymptote.el within Org Jarmo Hurri
2022-07-21 10:22 ` Munyoki Kilyungi
2022-07-22 7:28 ` Jarmo Hurri [this message]
2022-07-25 21:15 ` Munyoki Kilyungi
2022-07-25 21:15 ` Munyoki Kilyungi
2022-07-26 3:40 ` Greg Minshall
2022-07-26 9:52 ` Jarmo Hurri
2022-07-26 2:05 ` Ihor Radchenko
2022-07-26 10:09 ` Jarmo Hurri
2022-07-27 3:12 ` Ihor Radchenko
2022-07-27 3:13 ` Ihor Radchenko
2022-07-27 0:03 ` Tim Cross
2022-07-27 3:06 ` Ihor Radchenko
2022-07-27 4:09 ` Tim Cross
2022-08-18 16:04 ` Max Nikulin
2022-07-27 4:07 ` Jarmo Hurri
2022-09-01 7:52 ` Bastien
2022-09-03 13:25 ` Jarmo Hurri
2022-09-27 22:06 ` Bastien
2022-10-08 9:58 ` Jarmo Hurri
2022-11-09 6:21 ` Ihor Radchenko
2022-11-10 12:23 ` Jarmo Hurri
2022-11-13 4:27 ` Ihor Radchenko
2022-11-19 11:15 ` Bastien
2022-11-21 6:59 ` Jarmo Hurri
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=87tu791u93.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--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).