On Sun, Dec 10, 2017 at 6:13 AM, lewis <[email protected]> wrote:
> *Installing Leo* > > [snip] > *Quick and easy* > > [snip] > *Install Leo using pip* > [snip] > *Running Leo* > [snip] *Options for installing Leo.* > [snip] > *Dependencies* > [snip] > *Installing Packages* > [snip] > *Installing Leo with Git* > [snip] *Miniconda* > [snip] Many thanks for this all work. It shows a lot of care and thought. I apologize for the long delay in my comments. I thank Victor for his comments and Matt for his work on PyPi. As I understand it, Matt's work will make 'pip install leo' feasible. The problem I have with lengthy text, as I have cheekily summarized above, is that the text doesn't indicate the logical structure of the text. On a web page, I use local tables of contents to show that structure at the top of the page. That structure is apparent in LeoDocs.leo in the nodes that make up the topic. Would you be willing to a .leo file that contains proposed text, with the logical structure of the text mirrored in the node structure? It won't be huge, and you should be able to attach it to this conversation, perhaps with a .leo.txt extension. You can use any convenient markup, including markdown, to indicate links. I'll translate to rST markup later. Does that suit you? 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
