I don't know about your issue, but you just solved mine. I was having trouble running scripts from inside Leo, getting ImportError. I found the sys.path that nodes were seeing was a small subset of what was seen from a Python command line.
I did ~/.leo$ mv db db_hide which forced a db rebuild, and the problem went away After rebuilding ~/.leo/db all is well, and I'm quite sure Leo is opening more quickly. Seems like a good idea to occasionally do ~/.leo$ rm -rf db/ PS after restoring the old cache, ~/.leo$ mv db_hide/ db The prior error didn't return, so there's some magic afoot. On Tue, Aug 18, 2009 at 9:34 AM, Edward K. Ream<[email protected]> wrote: > > > > On Aug 17, 7:25 pm, "Edward K. Ream" <[email protected]> wrote: >> It appears that the last several revs of the trunk are damaged. There >> may be a problem with LeoPyRef.leo, but that's only a guess. >> >> Please don't commit until I can figure out what is going on. > > I think I know what is going on. The repository is apparently sound, > but Leo's caching seems somehow to be interfering with bzr reverts and > pulls. > > Here is what I think I know for sure: > > 1. Pulling lp:leo-editor into a branch with a *new* name always > works. > > 2. Pulling lp:leo-editor into a branch with an *existing* name fails > spectacularly on my machine. I delete the old branch, say main-trunk, > then do:: > > bzr pull lp:leo-editor main-trunk > > After that, when I load LeoPy.leo (created by copying leoPyRef.leo), > the outline is missing nodes. On my machine, for example, the > contents of the selfInsertCommand node is empty, as is all of its > descendant nodes. > > 3. Similar problems arise with updates such as:: > > bzr pull -r 2326 lp:leo-editor trunk > > 4. Regardless of whether the head or a specific revision is pulled or > merged, the quick test for whether the pull or merge was successful > is for me to open test.leo and look at the fonts in the body pane. My > typical (largish) fonts mean that the pull or merge went well. Odd > fonts means something went pretty drastically wrong. > > 5. I strongly suspect caching is the problem. If I pull a clean copy > of lp:leo-editor into a new (but previously existing) directory, > opening leoPy.leo does not re-read all the source files, but instead > uses cached values. After clearing all the contents home/.leo/db, > opening leoPy.leo does, in fact, re-read all the sources files. > > In conclusion, it does appear that the repository is ok, and that the > present head of the repository, rev 2333 does properly revert the > previous problematic code. OTOH, the evidence suggests a serious > problem, namely that Leo's caching can interfere with bzr revert and > pull operations. > > Your comments please. > > 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 -~----------~----~----~----~------~----~------~--~---
