There's no shame in having big data-changing commands not be undoable! Big software packages often have such commands!
On the other hand, it should be somewhat indicated when an action is not undoable. (perhaps add "This action is not undoable" in the string where the user is asked about refreshing from disk when an external file change is detected. idem for when an opened .leo file changes, and other non-undoable actions, when possible.) But the most important thing is to* wipe clear the undo stack when such an action occurs*, as undoing past an non-undoable action will corrupt the logical integrity and state of the outline with nonsensical structures and content. (as all other big software that i know also do as a standard) Félix On Thursday, July 13, 2023 at 12:53:17 PM UTC-4 Edward K. Ream wrote: > On Thursday, July 13, 2023 at 8:57:57 AM UTC-5 Edward K. Ream wrote: > > On Thu, Jul 13, 2023 at 7:49 AM Edward K. Ream <edre...@gmail.com> wrote: > > > On second thought, *none of *[the git-diff commands] *need to be > undoable*. > > > Otoh, undoing an accidental abbreviation is essential. It's the only hard > case, but I am confident that u.before/afterChangeGroup can do the job. > > 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/ce022749-26f3-4810-85f7-769a842c2f1an%40googlegroups.com.
