The g.new_config switch controls how Leo loads files and handles settings. When this switch is True, the code is substantially simpler in important ways. The new_config world is fundamentally better, but it could be slightly bugging for a short while.
Yesterday the new_config code started to work. I have been using it for several hours now, discovering and fixing minor problems along the way. Imo, the new_config code is almost ready for wider testing. The big switchover to the new_config code will happen soon. This will happen in three commits. The first two will happen one right after the other, the third will happen later today or tomorrow. 1. The last commit with new_config = False This will be a fallback in the highly unlikely event that should something seriously wrong be discovered in the new code. 2. The first commit with new_config = True The only difference between this commit and the previous will be that new_config will be True. 3. A commit with the g.new_config switch removed. This will remove the g.new_config switch *itself*. This will remove all code activated only when g.new_config is False, leaving only the code activated when g.new_config is True. This will significantly clean the code. ===== Summary These commits entail some risk. That can't be helped--it's time to take the plunge. Please let me know immediately if you have any problems with this plan. Time is running out ;-) Edward P.S. I intend to fix whatever glitches are found in the "new_config = True" world. It would be pointless to work in the "new_config = False" world any longer. The old world should be put down asap. EKR -- 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.
