From: Timothy <tecosaur@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Moving some lisp/ob-*.el files to org-contrib - your advice?
Date: Tue, 04 May 2021 01:49:31 +0800 [thread overview]
Message-ID: <87k0ofiu6t.fsf@gmail.com> (raw)
In-Reply-To: <87bl9rq29m.fsf@gnu.org>
This is only tangentally related, but this feels like a relevant place
to mention this and I don't think it deserves its own thread.
I think it's also worth considering deleting ob-julia.el from
org-contrib. Not to put to fine a point on things, but it's currently
dysfunctional. Trying to execute any code in a session causes Emacs to
freeze. Simply put, it was written for pre-1.0 Julia and is no longer
fit for purpose.
For the future, I'd think Julia actually warrants 1st class inclusion in
Org, and I've instigated an effort to write an ob-julia that works well.
More on this once it reaches a usable state.
-----
Regarding your the list of proposed files to move to org-contrib, I
concur that they fall under the bar you're setting.
Just going from the fact I haven't heard of them, perhaps ob-groovy.el,
ob-io.el, and ob-shen.el may be worth adding to the list?
--
Timothy
Bastien <bzg@gnu.org> writes:
> Hi all,
>
> Less code is less bug and less maintainance. So I'm considering
> moving these files to the new (unmaintained) org-contrib repo at
> https://git.sr.ht/~bzg/org-contrib:
>
> - ob-abc.el --- Org Babel Functions for ABC
> - ob-asymptote.el --- Babel Functions for Asymptote
> - ob-coq.el --- Babel Functions for Coq
> - ob-ditaa.el --- Babel Functions for ditaa
> - ob-ebnf.el --- Babel Functions for EBNF
> - ob-hledger.el --- Babel Functions for hledger
> - ob-J.el --- Babel Functions for J
> - ob-ledger.el --- Babel Functions for Ledger
> - ob-lilypond.el --- Babel Functions for Lilypond
> - ob-mscgen.el --- Babel Functions for Mscgen
> - ob-picolisp.el --- Babel Functions for Picolisp
> - ob-vala.el --- Babel functions for Vala evaluation
>
> I suggest a criterium for keeping ob*.el files in Org could be that
> the extension is known by Emacs _or_ that the supported language is
> well-established.
>
> Since I can obviously not decide alone about "well-established", would
> you mind giving your advice on whether the files above can be moved to
> org-contrib? (Of course we would advertize this carefully. And also,
> there is absolutely nothing personal about perhaps moving *your* file
> out of Emacs, it's just that maintainance will be easier outside.)
>
> Are there any other?
>
> I'll leave this thread open during this week, no need to rush here.
>
> Thanks,
next prev parent reply other threads:[~2021-05-03 17:53 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 15:13 Moving some lisp/ob-*.el files to org-contrib - your advice? Bastien
2021-05-03 17:49 ` Timothy [this message]
2021-05-03 18:05 ` Bastien
2021-05-03 19:36 ` Palak Mathur
2021-05-03 19:44 ` Timothy
2021-05-03 19:47 ` Palak Mathur
2021-05-03 20:34 ` Bastien
2021-05-03 20:33 ` Bastien
2021-05-04 7:55 ` Eric S Fraga
2021-05-19 3:36 ` Jack Kamm
2021-05-03 20:52 ` Victor A. Stoichita
2021-05-04 10:19 ` Dr. Arne Babenhauserheide
2021-05-04 11:28 ` Bastien
2021-05-04 18:38 ` Victor A. Stoichita
2023-07-12 13:40 ` [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?) Ihor Radchenko
2023-07-12 22:35 ` Jonathan Gregory
2023-07-13 6:52 ` Dr. Arne Babenhauserheide
2023-07-13 10:08 ` Ihor Radchenko
2023-07-13 11:04 ` Jonathan Gregory
2023-07-14 12:38 ` Jonathan Gregory
2023-07-14 13:15 ` Dr. Arne Babenhauserheide
2023-07-14 13:52 ` Ihor Radchenko
2023-07-14 18:06 ` Ihor Radchenko
2023-07-17 17:02 ` Jonathan Gregory
2023-07-18 9:38 ` Ihor Radchenko
2023-07-19 12:17 ` Jonathan Gregory
2023-07-20 7:13 ` Ihor Radchenko
2023-07-20 17:53 ` Jonathan Gregory
2023-07-21 7:36 ` Ihor Radchenko
2023-07-21 11:38 ` Jonathan Gregory
2023-07-22 8:12 ` Ihor Radchenko
2023-07-25 16:16 ` Henrik Frisk
2023-07-25 16:26 ` Henrik Frisk
2023-07-25 17:17 ` Jonathan Gregory
2023-07-25 21:40 ` Henrik Frisk
2023-07-25 17:29 ` Jonathan Gregory
2023-07-26 8:15 ` Ihor Radchenko
2023-07-26 12:35 ` Jonathan Gregory
2023-07-27 7:21 ` Ihor Radchenko
2023-07-27 12:42 ` Jonathan Gregory
2023-07-28 7:37 ` Ihor Radchenko
2023-07-28 14:02 ` Jonathan Gregory
2023-07-29 7:16 ` Ihor Radchenko
2023-07-31 11:14 ` Jonathan Gregory
2023-07-31 11:58 ` Ihor Radchenko
2023-07-31 12:42 ` Jonathan Gregory
2023-08-08 13:01 ` Ihor Radchenko
2023-08-10 11:05 ` Jonathan Gregory
2023-08-11 7:04 ` Ihor Radchenko
2023-08-15 7:33 ` Henrik Frisk
2023-08-15 10:41 ` Ihor Radchenko
2023-08-15 15:57 ` Henrik Frisk
2023-08-15 16:04 ` Ihor Radchenko
2023-08-16 12:54 ` Jonathan Gregory
2023-08-17 10:26 ` Ihor Radchenko
2023-08-19 12:56 ` Jonathan Gregory
2023-08-20 7:20 ` Ihor Radchenko
2023-08-20 12:47 ` Jonathan Gregory
2023-08-20 13:46 ` Dr. Arne Babenhauserheide
2023-08-21 7:48 ` Ihor Radchenko
2023-07-13 6:33 ` [BUG] WORG example for ob-lilypond is no longer working as described Dr. Arne Babenhauserheide
2023-07-13 7:03 ` Dr. Arne Babenhauserheide
2023-07-13 8:03 ` Jean Abou Samra
2023-07-16 12:21 ` Graham King
2023-07-16 12:30 ` Ihor Radchenko
2021-05-04 11:32 ` Moving some lisp/ob-*.el files to org-contrib - your advice? Bastien
2021-05-03 22:19 ` Tim Cross
2021-05-03 23:15 ` Bastien
2021-05-04 10:19 ` Dr. Arne Babenhauserheide
2021-05-04 11:10 ` Bastien
2021-09-26 8:17 ` Bastien
2021-05-06 9:19 ` Jean Louis
2021-05-06 9:39 ` Bastien
2021-05-14 18:23 ` Greg Minshall
2021-05-17 16:39 ` Greg Minshall
2021-09-26 12:50 ` Bastien Guerry
2021-10-02 17:11 ` Bastien Guerry
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=87k0ofiu6t.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=bzg@gnu.org \
--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).