Important: We often refer to outline nodes by the directives they contain. For example, an @root node is a node containing an @root directive, etc. Exception: An @file node is a node whose headline starts with @file.
Headlines that start with one of these create (correspond to) derived files. The following synonyms exist:
@asis, @file-asis @noref, @file-noref @nosent, @file-nosent
For more information, see the documentation for @asis, @auto, @file, @noref, @nosent and @thin in Leo's programming reference chapter.
@auto trees allow you to edit derived files that contain no sentinels. Leo will import the @auto files when reading .leo files. Be careful when first creating the @auto node. Before saving the .leo file containing the new @auto node, use the read-at-auto-nodes command to do the initial import.
Leo1 denotes all versions of Leo that write version 1 .leo files, that is, all Windows version of Leo prior to version 2.0. The last version of Leo1, version 1.15, understands enough about Leo2 to issue a warning when opening version 2 files.
Leo2 denotes all versions of Leo that write version 2 .leo files, that is, all versions of leo.py and all Windows versions with version number 2.0 and above. Only Leo2 can generate derived files from @file trees.
A node that would not be copied to a derived file. Orphan nodes can arise because an @thin tree has no @others or @all directives. Sections that are defined but not used also create orphan nodes.
Leo issues a warning when attempting to write an @thin tree containing orphan nodes, and does not save the derived file. No information is lost; Leo saves the information in the @thin tree in the .leo file. Leo will load the @thin tree from the .leo file the next time Leo opens the .leo file.
See Writing plugins and hooks.