Re: #561: Please explain why making Leo a jupyter client is important

I think it's also about building on Jupyter concepts as reproducible literate programming platform, not just cloning its current functionality See it as an alternative to the JupyterLab application (https://channel9.msdn.com/Events/PyData/Seattle2017/BRK11), reusing the same capabilities from

Re: #561: Please explain why making Leo a jupyter client is important

On Thu, Oct 26, 2017 at 8:51 AM, Terry Brown wrote: > > > Does this vision match yours? Here are some initial thoughts. > > My thoughts, which include a lot of groundless assumptions about how > Jupyter works, would be that we have a new node type: > ​[big snip] Thanks

Re: Merging leo_edit_pane into master?

On Tue, Oct 24, 2017 at 10:33 AM, Edward K. Ream wrote: > > ​> ​​I'll run my typical tests in the branch and let you know soon. > > ​Here are some minor problems.​ > ​I'm good with you merging this branch provided that you update LeoPyRef.leo and create a project describing

Re: Use projects to document git branches?

On Thu, Oct 26, 2017 at 7:44 AM, Terry Brown wrote: Either way - the "branch-notes" folder approach is part of the repo., > whereas projects are a separate github thing, but I'm sure there'll be > an API for downloading them, and branches are supposed to be transient >

Re: Rendering math in Leo

On Fri, Oct 27, 2017 at 12:15 AM, Matt Wilkie wrote: > Jumping in for just pandoc part of the thread: I happened upon `pypandoc` > today when looking in to better formatting of the Leo PyPi page overview: > https://pypi.python.org/pypi/pypandoc. A simple implementation of which