I am running into complications with the one-node world. This is no great surprise.
For starters, I have added a g.enableDB switch that turns off file caching. That way I have some hope of debugging read code :-) I plan to make this a command-line option. There probably should also be a command to clear the cache, excepting perhaps the LEO_EDITOR key. Another complication is that the tnodeList hack that underlies @file nodes. There has been some discussion of making @file work like @thin in a **backward compatible** manner. That is, Leo will read "legacy" @file nodes (and external files) as it has always done, but will write @file nodes exactly like @thin nodes. Does anyone have a big problem with this plan? The only objection I can foresee is that @thin sentinels are a bit more complex that @file sentinels, but imo this is not a strong enough objection. @file is an accident waiting to happen for shared repositories. Finally, I think pickleshare.py should be moved into Leo's core. It's used by Leo's core and is an essential part of caching. At present, it's pretty much hidden in the external directory, and furthermore, leoExternal.leo should be folded into leoPy.leo. 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 leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
