You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ob-python is a language that supports having persistent sessions that source blocks are run in. It's an awesome feature.
With elixir (well, because of erlang) we should be able to do nifty things like create two sessions, each a separate erlang node, and then run code snippets in either node.
When I mentioned using alchemist, I hadn't realized that elixir-mode also can run an IEx repl. I'd guess that if you're going to have a dependency, you can't go wrong with it being elixir-mode. Plus, alchemist depends on it :)
I was going to try and implement this like I did the previous PR -- by shamelessly ripping off ob-python. Suggestions welcome!
The text was updated successfully, but these errors were encountered:
I started the whole thing by shamelessly looking into ob-java.el in org sources, so please, go ahead with looking into ob-python.
And I agree that if we can avoid depending on alchemist that's probably better. Realistically though, I believe that almost every one using emacs and emacs-elixir is also using alchemist.
ob-python is a language that supports having persistent sessions that source blocks are run in. It's an awesome feature.
With elixir (well, because of erlang) we should be able to do nifty things like create two sessions, each a separate erlang node, and then run code snippets in either node.
When I mentioned using alchemist, I hadn't realized that elixir-mode also can run an IEx repl. I'd guess that if you're going to have a dependency, you can't go wrong with it being elixir-mode. Plus, alchemist depends on it :)
I was going to try and implement this like I did the previous PR -- by shamelessly ripping off ob-python. Suggestions welcome!
The text was updated successfully, but these errors were encountered: