First, don't panic: I am not going to do anything about this until after 5.0 final.
The perfect import checks ensure (in some hard-to-define way) that round-tripping (reading, then writing) any @auto file does not change in any *significant* way. When the the checks fail, Leo inserts an @ignore directive, and then refuses (with a dialog) to write the @auto file until the user explicitly removes the @ignore directive. An amazing amount of complexity is involved in the perfect import checks, as indicated by the weasel-words above. Determining when changes are significant must be done differently for each file type that @auto supports. Perhaps worse, the error message telling why the checks failed are a) extremely hard to generate in a helpful way and b) even harder, in general, for the poor user to understand. I am beginning to wonder whether all this caution is necessary. For those using git, it will be easy to check the import using git diff than with Leo. And git users can easily and quickly undo any unwanted changes. The @auto logic is, by far, the ugliest in Leo. It is riddled with impossible-to-remove special cases. It typically takes over an hour for me to come up to speed when fixing any @auto-related bug. Alas, this code is unlikely ever to go away. However, it would be easy to create a setting that would suppress perfect import checks. Your comments, please. 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/d/optout.
