Jean-Marc Lasgouttes wrote:
> What happens if the function decides to change nothing after all? We have a 
> useless
> undo step.

so if somebody pushes ctrl+z, one step nothing happens? undo machinery could
detect and kill empty start-end undo block at the end.

> recordUndo only applies to AtPoint lfuns, which is a bit strange. If I 
> remove the extra test for AtPoint flag
> it will apply to all cursor-related lfuns. We can do that, but it is an 
> invasive change.
>
> As you prefer.

no, you are the architect of undo machinery, so you decide :) i only wondered
whether one common undo call is not more safe then dessiminating it in many
different places, if you think its better, ok.

pavel

Reply via email to