Richard rejected _automatic_ adding of undo-boundaries for timers when
we discussed this earlier.
Treating *process output* this way might be ok. It is not the same
issue as the result of user editing commands.
___
Emacs-pretest-bug mailing
It seems to mostly have to do with shell buffers, commands that
generate lots of output, and yes, editing/manipulating large (I
wouldn't say huge) text files.
If you kept `undo-outer-limit' at its default value of 3M, I would
suspect problems in undo handling by
Joe Corneli wrote:
I think that running ogg123 on a .ogg file in the shell will do it. I
think running wget asynchronously to download a big file will do it.
If you are handling 3+M files, the warning is to be expected.
The messages also seem to appear when I edit (using emacs lisp) a
I think that running ogg123 on a .ogg file in the shell will do it. I
think running wget asynchronously to download a big file will do it.
If you are handling 3+M files, the warning is to be expected.
Actually, I don't see any reason why Emacs should complain about it.
Most likely what
Stefam Monnier wrote:
Most likely what should happen is that undo that's accumulated from
process's output should be chunked automatically.
E.g. we could add an undo-boundary after running a process filter, or from
an idle-timer.
I may have misunderstood in my previous reply. You
