I didn't mean that round-tripping could be a problem. I meant that it imposes extra steps, incurs a time delay, and adds distraction. These things get in the way of the work of composing and thinking out a notebook. As an example, here is how I typically develop Sphinx documents, which use ReStructuredText and the rst3 command. I will draft up a partial structure in Leo, then work on certain nodes. From time to time I will look at them with VR3 to catch any RsT syntax errors and make sure that the appearance seems right. Also I find that viewing a rendered view helps me to catch typos and other editorial errors, and even errors in flow and thinking.
Hi Thomas Thanks for your detailed explanation. I believe I understand what you mean: you want to create a smoother workflow, which is the real Leonine in your heart. Haha, I can see how deep your feelings for Leo are. I agree that a smoother workflow will bring a very good experience and allow people to experience the flow state when using Leo. My main concerns are, 1. This will increase the code workload and additional maintenance burden, 2. If no one uses this feature, just like the previous ipython bridge, no one will find that it doesn't work. Build it means waste of time. So I think, if more people use Leo and Jupyter/Jupytext, then it makes sense to add it, if not many people use it, keeping a basic rendering may be enough. What do you think? -- 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 view this discussion visit https://groups.google.com/d/msgid/leo-editor/7a7d7f84-3259-4848-ba60-be1c5324083dn%40googlegroups.com.
