On Feb 7, 7:18 am, "Edward K. Ream" <[email protected]> wrote:
> 1. Caching generates a lot of files in the .leo/db folder. My > present .leo/db folder contains about 27 meg of data. I am concerned > about the size of the folder. It looks like it has no natural size > limit. This following applies to both cached .leo files and cached external files. Once a file changes, it's unlikely that a formerly cached version of the file will ever again be used. But unless I am mistaken, the db folder never gets cleaned: cached files remain forever. A clean-cache command isn't the solution. My main idea is to associate cached items with both the files contents *and* the full path to the file. When updating a cached item, we would delete any previous item at the same path. This should be a simple, safe and effective optimization. My secondary idea is that there is actually very little involved in caching. I'm not convinced that pickleshare.py (and path.py, called by pickleshare.py) are needed. It may be simpler, safer and more flexible to create a leoCache module. Edward -- 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.
