As of rev 5309 of the trunk, Leo now supports @auto-otl, along with imports of .otl files.
**Warning**: the new code is simply a prototype. Play with these features *only* on files you can afford to be corrupted. To use @auto-otl: 1. The easy, and relatively safe way: - Use Leo's import-file command to create and populate an @auto-otl node. - Save the .leo file. 2. The manual, less safe way: - Create a node called @auto-otl x.y x can be an absolute path or a path relative to the directory containing the .leo file. - Save the .leo file, but **do not** overwrite the existing .otl file when prompted. Either way, you should create an @auto-otl node whose **children** represent the contents of the external .otl file. (The actual @auto- otl node is *not* written to the external file. This allows you to put Leo directives in the node.) Changing the children in Leo will change the external file. Changing the external file outside of Leo will update the outline the next time you restart the .leo file containing the @auto-otl node. **Important**: as with all kinds of @auto nodes, clone links will break the next time you load Leo if the @auto-otl tree contains any kind of cloned nodes. This is pretty much a fundamental limitation of @auto trees. However, if the VO people wanted to *retain* gnx's when editing in vim, it would, in theory, be possible to retain clone links when Leo read the external .otl file. I don't plan to do this any time soon, and it would require and extension to the VO file format, but I wanted to point out the possibilities. In any event, please report your experiences with @auto-otl asap. Thanks. 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.
