Called to indicate that the buffer operations between here and a
call to TextBuffer.endUserAction are part of a single
user-visible operation. The operations between
TextBuffer.beginUserAction and
TextBuffer.endUserAction can then be grouped when creating
an undo stack. gtk.TextBuffer maintains a count of calls to
TextBuffer.beginUserAction that have not been closed with
a call to TextBuffer.endUserAction, and emits the
“begin-user-action” and “end-user-action” signals only for the
outermost pair of calls. This allows you to build user actions
from other user actions.
The “interactive” buffer mutation functions, such as
TextBuffer.insertInteractive, automatically call begin/end
user action around the buffer operations they perform, so there's
no need to add extra calls if you user action consists solely of a
single call to one of those functions.
Called to indicate that the buffer operations between here and a call to TextBuffer.endUserAction are part of a single user-visible operation. The operations between TextBuffer.beginUserAction and TextBuffer.endUserAction can then be grouped when creating an undo stack. gtk.TextBuffer maintains a count of calls to TextBuffer.beginUserAction that have not been closed with a call to TextBuffer.endUserAction, and emits the “begin-user-action” and “end-user-action” signals only for the outermost pair of calls. This allows you to build user actions from other user actions.
The “interactive” buffer mutation functions, such as TextBuffer.insertInteractive, automatically call begin/end user action around the buffer operations they perform, so there's no need to add extra calls if you user action consists solely of a single call to one of those functions.