Re: @auto-md: multiple vnodes with gnx

Oh, you mean that the headline indent level should translate into the right number of "###" characters? You are right that an @clean file wouldn't do that. What would be just right is the rst3 command, except adapted for MD instead of RsT. I've been thinking there ought to be such a command.

Re: @auto-md: multiple vnodes with gnx

I do not import MD files, I create and write them in Leo. The bad about @clean files is, that they do not convert my node tree into a valid MD files containing headings with the right level. Or do they? On Sunday, August 27, 2023 at 9:05:16 PM UTC+2 tbp1...@gmail.com wrote: > One possibility is

Re: @auto-md: multiple vnodes with gnx

One possibility is to import an MD file as an @auto-md. This way you will get the sections set up as you expect. Then change it to be an @clean file, then save the outline. After this, the external file will always track what is in your outline (and if you edit the external file with some othe

Re: @auto-md: multiple vnodes with gnx

Ah, ok, I see: auto-xx nodes are NOT stored w/i Leo files. Hm, how can I overcome this. What I want is that all my MD is stored w/i my Leo file and when I save it, all MD-nodes should be written as they are now. At startup of Leo, Leo would not need to read MD files, because their content is st

Re: @auto-md: multiple vnodes with gnx

The behaviour I experience seems documented: https://leoeditor.com/FAQ.html#why-doesn-t-leo-support-cross-outline-clones - and that makes sense, if MD files are read by Leo. But why are they read? They only need to be written as I want to create MD files using Leo and only Leo. On Friday, Aug

ENB: Improving the python importer

PR #3515 contains preliminary work improving Leo's python importer. This work has uncovered several related issues. This Engineering Notebook discusses the way forward. *Background* The files in leo/plugins/importers contain all of Leo's