Leo 6.3.1 is necessary for two reasons: 1. There is a crasher in the leoflexx.py plugin. Somehow pylint did not detect that u.afterChangeNodeContents no longer uses the "dirtyVnodeList" kwarg. I am not amused.
2. More happily, I am working on a major simplification of Leo's undo code, per #1413 <https://github.com/leo-editor/leo-editor/issues/1413>. Imo, the new code should be an official part of Leo asap. PR 1725 <https://github.com/leo-editor/leo-editor/pull/1725> summarizes the new changes. The undo logic for changes to headline text has already collapsed. I expect that the undo logic for changes to body text will similarly collapse. True, I could delay point 2 to Leo 6.4, but my guess is that Félix would rather deal with the changes to Leo's api asap. I'll check with him soon. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/dcf175c7-a1c4-4190-8ef6-7e734f515979o%40googlegroups.com.
