From: stardiviner <numbchild@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ob-js and Indium
Date: Thu, 19 Dec 2019 16:45:28 +0800 [thread overview]
Message-ID: <8736dgg0uv.fsf@gmail.com> (raw)
In-Reply-To: <CAOo=t4c_vvhe8KB1xUkfVske-LZjHmtQ4_LjQ6ZNm6MW3vg3nw@mail.gmail.com>
Ezequiel Birman <ebirman77@gmail.com> writes:
> Hi all.
>
> I wanted to know if a JavaScript source block configured to
> use a session managed via
> https://github.com/NicolasPetton/Indium is currently
> supported.
>
> I believe the error I am getting is related to
> https://code.orgmode.org/bzg/org-mode/src/master/lisp/ob-js.el#L47
>
From Git log history, It seems is submitted by @Aaron Ecay, I used to added
Indium, skewer etc JS REPL support for ob-js. But seems those external package
APIs updated again. I think you can update by yourself. It's simple.
>
> where “(declare-function indium-run-node "ext:indium-nodejs"
> (command))” refers to a function named “indium-run-node” that
> does no longer exist
>
> https://github.com/NicolasPetton/Indium/commit/3e7f181dca115bccb0cb150fc753ca353be359e4#diff-76bee0dfd13edc6083c22f66c5711149
>
>
> There is an “indium-launch-nodejs” instead that works with
> the current client-server model for Indium.
>
> I'll try to replace “indium-run-node” for
> “indium-launch-nodejs” and provide a proper config for an
> ob-js REPL in a “.indium.json” but any pointers you could
> provide to me would be of great help.
>
> Thank you
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
prev parent reply other threads:[~2019-12-19 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:50 ob-js and Indium Ezequiel Birman
2019-12-19 8:45 ` stardiviner [this message]
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=8736dgg0uv.fsf@gmail.com \
--to=numbchild@gmail.com \
--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).