On Jul 31, 7:55 am, "Edward K. Ream" <[email protected]> wrote: > A supposedly innocent change appears to have corrupted the trunk, or > rather Leo's read/write logic. > > Please avoid the commits or pulls from the trunk until things are > resolved.
The problem appears to have been fixed. My apologies for this. If, by bad luck, you did pull the trunk recently, some work may be needed. On my machine, I had to delete a copy of the trunk: bzr pull --overwrite did not work properly. I thought it would be clever to delay asking for the Leo id in .leoID.txt until after the Leo outline has been shown, but that can lead to catastrophic read/write failures in the (unlikely, except in my testing) case that a) we are opening a real .leo file and b) .leoID.txt does not exist. Instead, I'll see if I can make sure that the dialog prompting for the id will use whichever gui is in effect. In other words, we want to make sure that the console prompt for the id *never* happens. This would be a much better plan than telling newbies that they have to start Leo the first time from a console ;-) 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.
