I just got a new laptop with Windows Vista and have been spending the
last few days migrating my life over to it.
I ran into the bug that has been mentioned a time or two caused by the
lack of the .leoID.txt file.
I inserted this at the beginning of the loadOnePlugin function in leo/
core/leoPlugins.py
if g.app.config is None:
print "No g.app.config, making stub..."
class StubConfig:
def getBool(self, c, setting):
return False
g.app.config = StubConfig()
This hack prevents leo from crashing and allows the gui prompt for a
leoID to come up. I think this is a better solution than asking users
to manually create the .leoID.txt file and figure out where it goes.
This isn't a good fix, but it is a decent temporary solution until the
real bug is fixed.
By the way, I tried for a while to figure out the proper way to submit
this fix... but bzr is just too confusing for me. What's the standard
way to submit fixes such as this?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
