emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: ian martins <ianxm@jhu.edu>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: ob-java and ob-haxe
Date: Thu, 03 Sep 2020 00:55:55 -0400	[thread overview]
Message-ID: <87wo1bfoh0.fsf@kyleam.com> (raw)
In-Reply-To: <CAC=rjb5wMwCGUQKqFCjLZwch+P+OTPOSrd+C9mi9VrLs1TiTeg@mail.gmail.com>

ian martins writes:

> I posted patches for ob-java and ob-haxe a couple months ago but there was
> no interest. I have been given access to push to contrib. If there's no
> objection I'll put them there.
> I'll rename my version ob-java-alt so it doesn't conflict with the official
> one. The contrib directory doesn't have a "testing" directory so I'll add
> one. I'll document them in worg.

My understanding is that there's been a move away from adding new
libraries to contrib/, instead preferring an ELPA for cases where core
isn't deemed appropriate.

Fixes and enhancements to ob-java are obviously appropriate for core.
And while it'd be fine to host ob-haxe separately, my impression is that
it too would be suitable for core.

I'm sorry your patches haven't gotten any reviews or other feedback.
I've sat down a couple of times to review the ob-haxe patch but haven't
ended up blocking off enough time to get anywhere.  I'll revisit it this
weekend.  Of course, any feedback from those that actually use haxe
would be appreciated.

  reply	other threads:[~2020-09-03  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 11:56 ob-java and ob-haxe ian martins
2020-09-03  4:55 ` Kyle Meyer [this message]
2020-09-03 13:29   ` ian martins
2020-09-04  9:50     ` Bastien
2020-09-05 11:34       ` ian martins
2020-09-05 13:04         ` Bastien
2020-09-05 13:43           ` ian martins
2020-09-05 14:06             ` Bastien
2020-09-23 12:37         ` Bastien
2020-09-23 12:38         ` 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:

  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=87wo1bfoh0.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ianxm@jhu.edu \


* 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


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).