Re: disabling undo boundaries

[David Kastrup]

address@hidden (Phillip Lord) writes:

> David Kastrup <address@hidden> writes:
>>
>> The problem _I_ see is that it is in general not just "a command" which
>> may touch another buffer, but also compilation buffers, timer events,
>> font lock and a number of other background activities not immediately
>> caused by key presses.
>
>
> I don't think this is an issue, because Emacs is single-threaded. So,
> all of these events happen *between* commands which, in general, means
> that an undo-boundary has gone onto the current-buffer anyway.

Not for self-insert-command.  Not for stuff like shell-command-on-region
that has to wait for material to arrive.

-- 
David Kastrup