6. There should be a way to show a view of adjacent or nearby nodes so that the user can make sure they work together as intended. Showing a fully rendered view of nodes' Markdown is a desirable bonus to avoid round-tripping to Jupyter.
Thank you Thomas for such a detailed thought. I prepared a post yesterday to promote Leo in other communities. Here is the link to my post <https://github.com/leo-editor/leo-editor/issues/4131> (I put it on github issues so that if you think there is something wrong, you can modify it directly). This post roughly describes my main use case - just using Leo to organize the logic in Jupyter ipynb files. I am a relatively heavy user of JupyterLab. Because JupyterLab provides real-time code completion, I basically don't write ipynb code in Leo, so editing and rendering are not a big problem (of course, it's good if there is). Of course, I think what you said `round-tripping` may be a problem. It is possible that users will feel a little messy when switching back and forth between Leo and JupyterLab. But I think this problem is not easy to solve. Considering that the return on investment may not be large enough, I am willing to endure this problem. In general, I am quite satisfied with the way I imagine using Jupytext. -- 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/057f063e-104d-4ff6-b9d2-55cb3effe9d1n%40googlegroups.com.
