emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: ian martins <ianxm@jhu.edu>
To: Bastien <bzg@gnu.org>
Cc: Org-Mode mailing list <Emacs-orgmode@gnu.org>
Subject: Re: org-babel support for haxe
Date: Sat, 5 Sep 2020 07:48:13 -0400	[thread overview]
Message-ID: <CAC=rjb5bfRPNqhmue_Lvn8LEXARJFRo+oE5SrQb-8m8=cBnXmA@mail.gmail.com> (raw)
In-Reply-To: <878sdoadpo.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

That makes sense.

It's probably enough to keep the languages page [1] complete and up to
date. External repos should already have docs with the code.

[1] https://orgmode.org/worg/org-contrib/babel/languages.html

On Sat, Sep 5, 2020 at 3:24 AM Bastien <bzg@gnu.org> wrote:

> Hi Ian,
> ian martins <ianxm@jhu.edu> writes:
> > Hello. The included patch adds org-babel support for haxe (https://
> > haxe.org/). It allows main class and function definitions to be
> > optional, accepts variables and supports babel functional mode.
> > Please review.
> I'm not an Haxe user, so I cannot review the functionnalities, but
> from a cursory look, it seems fine.
> After 9.4, we will probably remove some Babel libraries from Org's
> core: we still need to decide on what criterium, but one candidate
> is to remove a Babel library if the corresponding language is not
> supported within Emacs core itself.
> If we go that route, we also need to do a better job at promoting
> external Babel libraries: perhaps a page on https://orgmode.org/worg
> would help.
> 2 cents,
> --
>  Bastien

[-- Attachment #2: Type: text/html, Size: 1814 bytes --]

  reply	other threads:[~2020-09-05 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  4:37 org-babel support for haxe ian martins
2020-09-05  7:24 ` Bastien
2020-09-05 11:48   ` ian martins [this message]
2020-09-06 15:24 ` Kyle Meyer
2020-09-12 15:18   ` ian martins
2020-09-13 20:04     ` Kyle Meyer
2020-09-24 21:17       ` ian martins
2020-09-30 10:08         ` ian martins

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='CAC=rjb5bfRPNqhmue_Lvn8LEXARJFRo+oE5SrQb-8m8=cBnXmA@mail.gmail.com' \
    --to=ianxm@jhu.edu \
    --cc=Emacs-orgmode@gnu.org \
    --cc=bzg@gnu.org \


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