The code in leoViews.py is ready for testing by the truly adventurous. The code is still disabled by default.
Please report any problem (with *enabled* code) immediately. Read the following notes **carefully**, or suffer the consequences: - **Important**: this code is pre-alpha quality. Use it with extreme caution--preferably on a copy of one of your files. Be prepared to discard the file. - To enable the code, change the new_auto switch to True. It is in the section << atFile switches >> at the start of leoAtFile.py. - The code does *not* support already-exiting organizer nodes. Loading an @auto file will "promote" all children of nodes to be their siblings. It would be safer to wait until support for already-existing organizers is available, but the choice is yours. - The code does yet munge headlines to match what the importer will create. If the headline of an organizer doesn't match, the read code will not find the organizer node when re-reading the file. - It *is* possible to create organizer nodes. Saving the .leo file will create the appropriate @organizer: nodes in the @views tree. - The code warns if the severest consistency check fails, but does *not* disable the @auto tree by inserting @ignore. I do not recommend saving the .leo file in that case. - The code *does* move comment nodes into the nearest organizer node, if possible. 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.
