On Sun, Aug 1, 2010 at 12:23 AM, Edward K. Ream <[email protected]> wrote:
> I agree. > > I see that leoUserGuide.txt presently is just one huge rST file. I > don't see how that can be useful. It was useful when it had the @thin contents of the user guide, instead of having it all in .leo file. > I have had no luck just dumping everything below the User Guide node > into an @thin file: I get lots undefined section messages. �...@all > doesn't help. The problem is that documentation, by its very nature, includes lots of stuff like this: << your section reference here >> Leo parses this as an actual section reference and complains loudly when it obviously doesn't see the correct child node. There might be a way to say that "this node contains no Leo markup, do not do any parsing here", but I don't know it. PS. Someone might also find this error message funny: "@ignore node: Why can't I use @ignore directives in @thin trees?" (perhaps @ignore logic should just look at beginning of headline?) -- Ville M. Vainio @@ Forum Nokia -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
