I use ReST more than MD, but they should work the in a similar way. For Leo trees that are intended to be used by Sphinx, I just make the headline of the top node start with @rst. Otherwise I just put @language rest in the body of the top node of the tree. The rst3 command creates a ReST file, and this works correctly even if you have several @rst nodes within the tree. You don't need external files at all. I thought there is or was going to be a similar command for md, but I don't find it in the codebase. There is a writer for writing @auto-md trees that probably does what you want. It writes an external file when you save the outline. I'm not sure about handling the clones, though. If you use @auto-md, I think they would also work automatically.
BTW, in case you don't know about it yet, the *viewrendered3* plugin will let you preview your rendered markdown within Leo, and even export the rendering to the system browser. This helps you to quickly spot mistakes in your markdown and try out syntax questions. On Sunday, April 2, 2023 at 10:31:36 AM UTC-4 p.os...@datec.at wrote: I recently started to document some of my Python projects using MkDocs and mkdocstrings. I write all markdown text using Leo, of course.That makes it possible to use clones for stuff being important to more than one MkDocs document. Alas, all clones are just copied on import (of course) and the clones are kinda broken (lost). Is it possible to store Markdown-file content in Leo somehow? Leo then would only export the md. There'd be no need to import. My clones would be preserved. Cheers Paul (using Leo since 2003). -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/02d24b47-27ad-4ca9-9b8b-ce691d3e343an%40googlegroups.com.
