comparison src/undo.c @ 59791:fc2f566fb0fd

(syms_of_undo) <undo-outer-limit>: Doc update.

59790:85fb49e8bc60

  undo_strong_limit = 30000;

  DEFVAR_LISP ("undo-outer-limit", &Vundo_outer_limit,
	      doc: /* Outer limit on size of undo information for one command.
At garbage collection time, if the current command has produced
more than this much undo information, it asks you whether to delete
the information.  This is a last-ditch limit to prevent memory overflow.

The size is counted as the number of bytes occupied,
which includes both saved text and other data.

In fact, this calls the function which is the value of
`undo-outer-limit-function' with one argument, the size.
The text above describes the behavior of the function
that variable usually specifies.  */);

59791:fc2f566fb0fd

  undo_strong_limit = 30000;

  DEFVAR_LISP ("undo-outer-limit", &Vundo_outer_limit,
	      doc: /* Outer limit on size of undo information for one command.
At garbage collection time, if the current command has produced
more than this much undo information, it discards the info and displays
a warning.  This is a last-ditch limit to prevent memory overflow.

The size is counted as the number of bytes occupied, which includes
both saved text and other data.  A value of nil means no limit.  In
this case, accumulating one huge undo entry could make Emacs crash as
a result of memory overflow.

In fact, this calls the function which is the value of
`undo-outer-limit-function' with one argument, the size.
The text above describes the behavior of the function
that variable usually specifies.  */);