Leo's rst3 command is being executed primarily for a "side effect", that is, @rst trees typically are being used merely to generate so- called "intermediate files" that get sent to docutils or sphinx. I believe I had lost sight of this fact in all the programming details.
As I said in another thread just now, it is quite possible to do simple things simply in @rst trees: Leo's own docs prove that. Complications arise because people want to generate rST sources from (clones of) actual source code. That is a perfectly reasonable goal, but the present way (code and doc mode and related tweaks) is horrendous. The options are obscure, complex and they interact in wretched ways. This is the opposite of true power and generality. The challenge seems daunting. If we are going to use actual source code, we appear to be limited to controlling the action using either global options or options defined in the source code itself using @rst- options doc parts. To summarize the present situation, we seek ways of generating *arbitrary rST code* from Leo trees that contain *computer source* code, not typical rst or sphinx sources. If we are looking for power, it would be good to focus on the word "arbitrary" in the phrase "arbitrary rST code" above. This suggests that **endless options** will not suffice. And indeed, even if we had endless options few programmers would tolerate sullying their sources for the sake of @rst trees into which the sources might be embedded! This seems like a dilemma: we can't change the programming sources much, and yet we want to generate *arbitrary* rST output from them! It looks like the only recourse are endless options, that is, options sufficient to generate everything that *in practice* we could ever want. It is this kind of thinking that has lead the present (unacceptable) situation. Something different is needed. The next post will explore some ideas... 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.
