I understand it's advised against to have a clone across 2 thin files. However, @thin qtNotes.txt does exactly this. This makes me slightly nervous, since I never commit that file (or anything apart from .py files in the first place), and I'm afraid sometimes valuable code in .py file could be thrown away because code in .txt file will take precedence.
Perhaps qtNotes.txt stuff should be moved to plain tree in .leo file, as opposed to @thin node? Also, perhaps there should be a loud warning when the user does this. It's a fact of life that in VCS environment, files *will* get out of sync. Some of these concerns could be solved by this ingenious hack (correct me if there is something like this in place already): Do not read in @thin nodes in tree order - rather, read them according to the extension, and have .txt mean "read this node last". Users could be advised to hold all their "note collector" trees as .txt files (and warned accordingly if this is not the case). -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
