From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: The fate of ob-asymptote.el
Date: Sat, 30 Jul 2022 12:23:49 +0300 [thread overview]
Message-ID: <87o7x7x8be.fsf@iki.fi> (raw)
In-Reply-To: 87fsil9upn.fsf@localhost
Hello Ihor.
Ihor Radchenko <yantar92@gmail.com> writes:
> Well. You convinced me. If Asymptote has very stable syntax and major
> features, it probably makes more sense to maintain it within Org or
> within Org community.
If Bastien shows the green light, I am looking forward to giving back
something to the community: maintanance and a good set of illustrative
examples on worg. For the past 2 years I have just been utilizing what
you guys have been doing, in a state of haze, for obvious reasons.
>> - I embrace a (any) maintained feature which extends the
>> applicability of Org without compromising "the core." I have had
>> great moments noticing that Org already supports something new I
>> need.
>
> I agree that it is nice, but we cannot, unfortunately support all the
> programming languages out there. As long a some specific language has
> a maintainer, things are fine, but in long term it is only reliable to
> support popular ones + possibly GNU projects (as Org is a part of GNU,
> and it is kind of obligation).
Makes sense. As long as there is a maintainer, a more exotic language
can be supported. Perhaps my contribution will increase the popularity
of Asymptote within the Org community and therefore the probability of
long term survival of ob-asymptote.el.
> As long as there is a person maintaining ob-asymptote, things should
> be fine. Especially if there is a good test coverage and WORG
> documentation.
I will be in standby mode until Bastien tells me what happens next.
All the best,
Jarmo
prev parent reply other threads:[~2022-07-30 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:55 The fate of ob-asymptote.el Jarmo Hurri
2022-07-20 15:18 ` Tory S. Anderson
2022-07-20 19:43 ` Nick Dokos
2022-07-21 5:17 ` Jarmo Hurri
2022-07-21 11:54 ` Ihor Radchenko
2022-07-21 13:21 ` Max Nikulin
2022-07-22 0:27 ` Ihor Radchenko
2022-07-22 7:12 ` Jarmo Hurri
2022-07-26 1:46 ` Ihor Radchenko
2022-07-26 10:23 ` Jarmo Hurri
2022-07-27 3:24 ` Ihor Radchenko
2022-07-27 7:31 ` Jarmo Hurri
2022-07-28 14:29 ` Ihor Radchenko
2022-07-30 9:23 ` Jarmo Hurri [this message]
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=87o7x7x8be.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).