all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: nerditation <nerditation@outlook.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emlua: a way to run a Lua interpreter inside Emacs as a module
Date: Tue, 29 Mar 2022 00:45:16 -0300	[thread overview]
Message-ID: <CADs++6hRov3GaKp77u9gbnzt2cJQfDCjPjth6WoT-75v6czigQ@mail.gmail.com> (raw)
In-Reply-To: <E1nZ2WI-0000U7-TG@fencepost.gnu.org>

On Tue, 29 Mar 2022 at 00:27, Richard Stallman <rms@gnu.org> wrote:
>   >   Emlua: a way to run a Lua interpreter inside Emacs as a module
>   >   https://github.com/edrx/emlua
>
> Is it already possible to run lua itself in a subprocess?

Yes, that's very easy, and that's what I did for many years.

> I have a feeling that linking all the world's language interpreters
> into Emacs itself is asking for (1) lots more work and (2) trouble.

I linked Lua because it is my favorite language and in most cases I
write Lua code much faster that I write Lisp... and I _did_ try to
write hooks to process the output of an inferior Lua process to write
code that would process some kinds of outputs as sexps, but failed.

Emlua is a personal project that is helping me to bypass some of my
limitations with writing hooks and filters in elisp. I hope that it
won't make people blame me for the next 1000 languages that will be
linked to Emacs using modules... =/

  Cheers,
    Eduardo Ochs
    http://angg.twu.net/#eev



  reply	other threads:[~2022-03-29  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27 23:00 Emlua: a way to run a Lua interpreter inside Emacs as a module Eduardo Ochs
2022-03-29  3:27 ` Richard Stallman
2022-03-29  3:45   ` Eduardo Ochs [this message]
2022-03-31  4:26     ` Richard Stallman
2022-03-29  3:46   ` Po Lu

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

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

  git send-email \
    --in-reply-to=CADs++6hRov3GaKp77u9gbnzt2cJQfDCjPjth6WoT-75v6czigQ@mail.gmail.com \
    --to=eduardoochs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=nerditation@outlook.com \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.