On Friday, July 14, 2023 at 8:24:17 AM UTC-4 Edward K. Ream wrote: On Fri, Jul 14 vitalije wrote:
> I just wished to illustrate how dangerous and tricky things can get when we have mutable state buried so deep down in the foundations of Leo's code. I agree. That's what PR #3438 <https://github.com/leo-editor/leo-editor/pull/3438> fixes, as follows: - The undo code for parse-body now uses bespoke undo/redo code. - All commands that previously used the retired "change tree" logic (u.before/afterChangeTree, etc.) now use the undo/redo insert-node logic. Does this mean that code in, say, an existing plugin won't work if it uses the currently-existing before/afterChangeTree calls? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/981cd2e4-14aa-4dec-b295-ccb904f848e5n%40googlegroups.com.
