On Jun 20, 11:15 am, "Edward K. Ream" <[email protected]> wrote: > For reference, here is my present thinking about what an external file > will look like:
> #...@+leo-ver=5-thin > #...@leo-data <list of gnx's> > #...@node 1 * @thin sentinels_test.py > #@@ > # This is a doc part. > #...@c should that be: #@@c > > #...@+<< a >> > #...@+node 2 ** << a >> > a > #...@-<< a >> > > #...@+others > #...@node 3 *** a-1 > a-1 > #...@node 4 *** a-2 > a-2 > #...@-others > > b where did this b come from,? Doesn't any non-leo housekeeper text have to be from some node's bodytext? > #...@+others > #...@node 5 ** 1-1 > 1-1 > #...@node 6 *** 2-1 > 2-1 > #...@node 7 **** 3-1 > 3-1 > #...@node 8 ** 1-2 > 1-2 > #...@-others > > Notes: > > 1. Some further comments about node sentinel lines. The form of the > line is: > > #...@node <index> <level> <headline> > > For example: > > #...@node 7 **** 3-1 <index> is going to be the base 62 character index, right?, your just using integers here for illustration purposes? > > I think this is about as good as can be. The node number is necessary > to resolve clones. The level indicator is the clearest possible > representation *for humans*. The headline is real data, and is always > a useful comment. We could abbreviate @node to, say, @!, but imo @node > is much easier for humans to understand. > > 2. The example does not use the ';/:' convention to indicate that the > body text of a node does not end in a newline. I'm not sure whether > this is a feature or a bug. Either way, whitespace clearly delimits > the <index> and <level> fields from the <headline> field. > > 3. As before, @others and section references have terminating > sentinels. This is required because those constructs embed the > contents of nodes in the body text of another node. > > 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.
