On Wed, Oct 23, 2024 at 7:25 PM HaveF HaveF <[email protected]> wrote:
> I have to say @jupytext is an amazing idea. Thanks. Our two posts crossed in the ether. It's been a great day. @jupytext has *already* proven its worth. > I wonder if it would be better to let the user choose whether to write to an external file or not? @jupytext always reads from an .ipynb file and writes to an .ipynb file. The paired .py files that jupytext writes (when using Jupyter) *no longer exist*! Indeed, it's best to delete any paired (.py) files. Their timestamps confuse Jupyter. As a bonus, Jupyter users should *NOT* use jupytext from within Jupyter! It doesn't get any better than that. Edward P.S. I'll soon augment the present prototype code with Leonine settings that control jupytext formats, etc. Everything important *works right now* except for round-tripping outline structure. That is, the present code only reads and writes the body text of @jupytext nodes. *Leo's @clean logic will soon read, write and update the entire @jupytext tree.* But not today. It's time for a break! 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS1NhUc0aPUgn6HrxhAyCTFfS4cGnrifuhe_cnYQnYLNXw%40mail.gmail.com.
