Re: [Emacs-diffs] fix/no-undo-boundary-on-secondary-buffer-change c7a6601 1/5: undo-size can count number of boundaries.

[Stefan Monnier]

>> and do it right before we add something to the undo-list (so the test of
>> undo_list indeed tells us if this is the first new change pushed since
>> the last boundary).  It should give us the same behavior but without the
>> need for that variable.
> Because, that triggers the hook only after a boundary.  With
> "undo-buffer-undoably-changed", the hook is triggered after
> undo-buffer-undoably-changed is set to nil which may or may not relate
> to the addition of a boundary. And actually, currently it doesn't.

So the question becomes: why doesn't it?


        Stefan