Subject: Documented the <<UndoStack>> event

From: fvogel <[email-masked]>
Date: Thu, 12 May 2016 21:22:57 +0000

---
 doc/event.n | 4 ++++
 doc/text.n  | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/doc/event.n b/doc/event.n
index 045339e..54ad42e 100644
--- a/doc/event.n
+++ b/doc/event.n
@@ -352,6 +352,10 @@ user-driven
 .QW "tab to widget"
 action.
 .TP
+\fB<<UndoStack>>\fR
+This is sent to a text widget when its undo stack or redo stack becomes
+empty or unempty.
+.TP
 \fB<<WidgetViewSync>>\fR
 This is sent to a text widget when its internal data become obsolete,
 and again when these internal data are back in sync with the widget
diff --git a/doc/text.n b/doc/text.n
index c788fa5..96e7ccc 100644
--- a/doc/text.n
+++ b/doc/text.n
@@ -897,6 +897,10 @@ separator is already present at the top of the undo stack no other will be
 inserted. That means that two separators on the undo stack are always
 separated by at least one insert or delete action.
 .PP
+The \fB<<UndoStack>>\fR virtual event is generated every time the undo stack
+or the redo stack becomes empty or unempty. This event is generated once for
+each peer widget.
+.PP
 The undo mechanism is also linked to the modified flag. This means that
 undoing or redoing changes can take a modified text widget back to the
 unmodified state or vice versa. The modified flag will be set automatically to
-- 
cgit v0.12