unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ian martins <ianxm@jhu.edu>, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ob-haxe
Date: Mon, 18 Jan 2021 07:27:44 +0100	[thread overview]
Message-ID: <878s8qu5cv.fsf@Otto.invalid> (raw)
In-Reply-To: <jwv7dobjip4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 17 Jan 2021 17:41:52 -0500")

Stefan Monnier writes:
> I'd be happy to do that, but just to be sure, I'd like to understand
> something first.  AFAICT, all other `ob-<LANG>.el` files are currently
> bundled with Org.

They aren't, there's quite a bunch of them that aren't properly inside
Org and of those that are, just a selected set is in Org core (only
those should be in Emacs by default).  The reasons are diverse, but for
a package to considered for core it must have copyright assigned to FSF,
suppport the complete feature set as far as the underlying language or
interpreter allows for it (i.e. session mode) and have an active
maintainer (Bastien or Nicolas can give you the "official" line on
that).  Secondary considerations are how common the language supported
really is and what it takes to set up an environment where you can
actually run tests.

> Personally, I'd tend to consider that the
> language-specific info for org-babel should belong with the major mode
> (just like the language-specific support for indentation, highlighting,
> flymake, imenu, etc.. belong to it).
> [ Side note: I'm not sufficiently familiar with org-babel to know if
>   bundling the info with the major mode is currently technically
>   realistic.  ]

Let's put it this way: I haven't seen any major mode that does that so
far.  I think the idea merits consideration, but as long as nobody tries
we don't really know what the pitfalls are.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs



  parent reply	other threads:[~2021-01-18  6:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 12:48 [ELPA] New package: ob-haxe ian martins
2021-01-17 22:41 ` Stefan Monnier
2021-01-18  3:35   ` ian martins
2021-01-18 16:31     ` Stefan Monnier
2021-01-19  5:30       ` Richard Stallman
2021-01-19 14:19         ` Stefan Monnier
2021-01-19 14:28       ` ian martins
2021-01-19 15:15         ` Stefan Monnier
2021-01-20  3:25           ` ian martins
2021-01-20  4:01             ` Stefan Monnier
2021-01-18  6:27   ` ASSI [this message]
2021-01-18 16:32     ` Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s8qu5cv.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-devel@gnu.org \
    --cc=ianxm@jhu.edu \
    --cc=monnier@iro.umontreal.ca \
    /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.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).