Reading your responses I noticed my own mistake: > - Separate code from outputs. One of the main strengths for Leo, combining code and results into the same document, is also one of its main limitations.
I meant " One of the main strengths for **Jupyter**, combining code and results into the same document, is also one of its main limitations." I guess I was suggesting exploring the use of clones to allow saving vanilla code/documentation in one file and output for a particular execution (possibly with sentinels) in another file, intermingling them in the same "notebook" tree during edition/visualization time. Presenting them together is convenient for delivering the notebook as a whole reproducible document, but storing them in the same file produces code fragmentation and other issues mentioned. Thanks for your comments -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
