🚀 go-pugleaf

It's not so much the size of the document that matters as the number of actions the script does that must be remembered for undo.

Watching the way that Find/Change handles this has me envious. It will undo a huge search with a single Command-Z. So it must have some way of essentially taking a snapshot, switching off the undo mechanism, doing its thing and then switching it back on again. Whatever, no matter how many changes there are, only one Undo is needed to get back to where you were.

I wish such a capability were available to scripters so that a script could choose between undo each step and undo the whole. If you chose the latter, then the undo mechanism would remember the state at the start of your script and at the end and nothing in between.

The way to speed up a script is to save the document occasionally to flush the undo cache.

Dave