Thanks Edward, that clears that up for me.  I still find it a bit odd that 
there was an announcement that Leo now supports jupyter, without any 
account of what the support consisted of and whom it might be useful for.

Leaving aside this specific example, I think my overall point about another 
component of documentation is still valid, even if I'm having trouble 
formulating it.  Maybe a better way to say it would be to break Tutorials 
into "for the committed" and "for the curious".  In the latter, experienced 
Leo people could be encouraged to write simple examples of "How this Leo 
feature helps me to accomplish the things I actually use a computer for."

Best,   geoff

On Saturday, 9 November 2019 07:30:27 UTC-3:30, Edward K. Ream wrote:
> On Sat, Nov 9, 2019 at 3:52 AM Geoff Evans < 
> <javascript:>> wrote:
> Okay, the basic question:  What is a very simple .leo file that will 
>> create a .ipynb file for a notebook with one markdown cell and one code 
>> cell that reports the outcome of some calculation?
> Leo doesn't provide that kind of support, and none is planned at present.
> Leo's ipynb importer and corresponding writer allow limited 
> round-tripping.  It's probably not all that useful.
> You could define an abbreviation that would create an empty Jupyter 
> notebook, but that would likely be of even less use.  Far better to create 
> your notebooks in Jupyter.
> 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 view this discussion on the web visit

Reply via email to