On Wed, May 21, 2008 at 1:41 PM, Kent Tenney <[EMAIL PROTECTED]> wrote:
> > Leo acts like it's treating the --config-single... > as a filename to open. The fix, I hope, is on the trunk. Only tested on XP: Linux machine unavailable for awhile. During testing I discovered the possibility of a major source of confusion. It appears that import leo.core.whatever will use the version of leo in python\Lib\site-packages initially, and then start using the "local" version of Leo after sys.path is updated. Or something like that. Not sure what the fix is. Presumably if you are in folder x and x\leo exists, then import leo.core.whatever should use the code in x\leo\core\whatever. Otherwise, if x\leo does not exist the leo package code should be used. Getting this to happen during startup may be tricky. In them meantime, you can save yourself a lot of confusion by *not* making Leo a package. 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 -~----------~----~----~----~------~----~------~--~---
