On Fri, 26 Mar 2010 12:41:57 -0500 Terry Brown <[email protected]> wrote:
> Anyway, with some valuable notes in that tree and unsaved changes in others I > accidentally double clicked a large binary file, cause active_path.py to try > and load it into a @shadow node with @auto parsing. After waiting a few > minutes for it to return I went to lunch, and fortunately it had returned > when I got back. I carefully deleted the containing directory entry. A similar problem occurs when you try and index a directory which contains 4823 subdirectories (just counting directories, not files). Not quite sure what the best solution is. Simplest is probably to have active_path.py bail after adding some number of directories, or perhaps after some amount of time has elapsed. The user can manually burrow down and expand things in more managable chunks. I think Leo can handle trees with 4823 nodes, but creating them with the naive approach active_path.py uses is probably too slow. Generating some sort of 'saved' format like JSON (I think Ville started this) and having Leo slurp that might be quicker. So another note to self. Cheers -Terry -- 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.
