Re: timers and undo

[Stefan Monnier]

> This is because it sees that the previous command was also `undo'.
> So it continues the undo sequence previously started.

> One fix is to make the command `undo' defensively notice that the undo
> list has changed since its previous execution.  Does the fix below
> give good results?

You could use the info that's already in undo-equiv-table (and which uses
a weak hash table so there's no impact on the GC behavior) to check whether
changes have occured since the last undo command or not (I use it here to
allow the user to continue a previous undo sequence even if it was
interrupted by some cursor movement).


        Stefan