On Monday, March 26, 2018 at 11:50:15 AM UTC-5, Edward K. Ream wrote:
> There are several problems with the vs- commands.
I am thinking that these commands might move into the mod_scripting plugin,
or the jupyter plugin (see below). There is lots of room for
experimentation. For example, an enhanced execute-script command would
know about:
>>> and <<< and sentinels
org-mode sentinels
Enhanced @language directives that carry optional arguments
> True, fully integrated, support for Jupyter will require a *Jupyter gui
plugin*.
Well, maybe not. The jupyter.py plugin might just do the following:
- Init one or more jupyter kernels in the background.
- Enhance the execute-script command so that it passes code/expressions to
a kernel.
- Show the result in, say, the VR pane.
- Define various commands in a Jupyter menu.
One can imagine doing all this in a week or three.
> I am now studying the Jupyter sources intensely
Happily, there are no odious side effect to importing jupyter code. This
is crucial. It means that all jupyter code is actually available.
> the handle_image* methods do a lot of image-related magic behind the
scenes.
I expect that these actual methods, or similar (they are small), will
eventually be used in the jupyter plugin.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
