The more I think about it, the more I think the advanced stuff in the rst3 command should be removed. I won't do this without consulting you all. It's not quite as evil as @root.
But it's not good. Code mode corrupts both the docs and the code. Worse, the present advanced options do a poor job. For example, they don't use Sphinx's markup such as .. py:module::, etc. Worst of all, the advanced stuff does, inevitably, make the rst3 command seem much harder to use than it really is. In this respect, there is a close parallel with @root. Imo, the vast majority of rst3 users would be much better off if we "offloaded" the task of converting programs to web pages. Happily, this suggest a clean solution. Suppose I create an example @button node that formats a selected outline (presumably containing source code) in a fairly flexible way? This might contain code switches corresponding to code-mode options. It would show how to parse doc parts, including markup and options doc parts. It would provide an easy way to do just about anything somebody would ever want to do with Leonine code. It might even be a better alternative to Leo's various export commands. Let's be clear. This would be a significant simplification for most users of the rst3 command. And it would simplify the rst3 code. Your comments please. I will do *nothing* with either code or docs until I write the @button script. This script will be my teacher. Edward -- 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.
