For several directives, a distinction needs to be made between their behavior with @root and @<file> directives. For instance, "When writing external files, Leo writes doc parts as comments." is not the behavior of @root, unless @bool print_doc_flag is changed from the default False to True - and then there are repercussions to untangle (do unit tests before changing the default). @delimit is not valid within @root. @language and @comment behave differently than the reference describes when used with @root.
@root must appear in the body, not the headline. @all is valid in @file and @shadow trees In the description of @code, a typo leaves out the c in @c. @file should note that people who continue to use 4.6 (e.g., because the latest Red Hat EL does not include sufficiently modern libraries) can no longer read the file if the file gets touched by 4.7, but that @thin is safe. If you are reading from the root toward the child (left to right) a relative @path adds to the path suffix. If you are reading from the child to the root (right to left), a relative @path adds to the path prefix. Either that needs to be explicit, or one may infer that the readers of an document in English should be told the former. It would be nice to have a table specifying which directives are valid in the headline and which in the body (or both). -- 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.
