The recent reorg of LeoDocs.leo (more is to come, see below) points the way to a clear, easy organization of the tutorial. I saw this when I awoke this morning.
Imo, the first part of the tutorial should explain @all, but *not* @others. This keeps the first part easy and short, and allows *all* programming details to reside in the third part. Indeed, non-programmers often use @all. For example, LeoDocs presently uses @all in all @file nodes. However, I am about to remove most @file nodes in LeoDocs, leaving only the corresponding @rst nodes (the rst3 command create external files automatically from @rst nodes, a fact that will be explained in the second part of the tutorial. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
