Yes, the <<node>> in rst would be useful, for the same reasons it is useful in code.
The work-around is to use an extra layer... In live code: <<Name>> .....<<Name>> whose body has @others ................@rst-no-head Name .... whose body has the code In an @rst tree: first heading next heading, which has at the end: .. code-block:: .......@rst-no-head Name (cloned) The terminal cloned node is inserted into the rst tree and the live <<Name>> can be put properly into any place in the live code. It isn't very convenient to have that extra level in live code, nor having to put in the the cloned node as the last node of its parent. What would be nice, is to allow within the @rst tree <<nodes>> that mean just what they do in the live code: insert this text at the indicated spot. I'll bet it is no more than a tweak to add that functionality (since it is done for the live code)... Then we could write: In live code (as usual): . . . <<Name>> .....<<Name>> .... whose body has the code In an @rst tree: heading .. code-block:: <<Name>> .......... <<Name>> (cloned node) . . I will try to rummage around in the rst3 code and see if that is a simple tweak. On Oct 11, 1:41 pm, Offray Vladimir Luna Cárdenas <[email protected]> wrote: > Hi, > > Your idea of live code and @rst was also what I intended. In fact I > recently wrote a mail about the use of <<nodes>> markup to get live > documentation (inspired by the experience of Smalltalk). I don't know > why this feature was disabled (of if it was enabled at some point), but > this way of live docs would be a really helpful feature rooted on leo's > background and definitely would improve reading a lot. > > Cheers, -- 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.
