*** empty log message ***

diff --git a/lispref/hooks.texi b/lispref/hooks.texi
index 3776f329d6681922853e19bcc161ee19da8fd4ab..7905e0904b34b8d3bad2e02adb0a1003bf834c89 100644 (file)
--- a/lispref/hooks.texi
+++ b/lispref/hooks.texi
@@ -32,12 +32,14 @@ are passed arguments, or else their values are used).
 @table @code
 @item activate-mark-hook
 @item after-change-function
+@item after-change-functions
 @item after-init-hook
 @item after-insert-file-functions
 @item after-make-frame-hook
 @item auto-fill-function
 @item auto-save-hook
 @item before-change-function
+@item before-change-functions
 @item before-init-hook
 @item before-make-frame-hook
 @item blink-paren-function
@@ -82,6 +84,7 @@ are passed arguments, or else their values are used).
 @item mh-letter-mode-hook
 @item mim-mode-hook
 @item minibuffer-setup-hook
+@item minibuffer-exit-hook
 @item news-mode-hook
 @item news-reply-mode-hook
 @item news-setup-hook

diff --git a/lispref/text.texi b/lispref/text.texi
index ccf43e72da60a26f4c057f0e8f123d152c2962f0..54ba73353ab1accec94e0b5a2cd904fd854bfc69 100644 (file)
--- a/lispref/text.texi
+++ b/lispref/text.texi
@@ -2192,6 +2192,12 @@ appear on the screen.  This works much like selective display.  Details
 of this feature are likely to change in future versions, so check the
 @file{etc/NEWS} file in the version you are using.
 
+@item intangible
+@kindex intangible @r{(text property)}
+A non-@code{nil} @code{intangible} property on a character prevents
+putting point before that character.  If you try, point actually goes
+after the character (and after all succeeding intangible characters).
+
 @item modification-hooks
 @cindex change hooks for a character
 @cindex hooks for changing a character
@@ -2624,29 +2630,39 @@ data if they do anything that uses regular expressions; otherwise, they
 will interfere in bizarre ways with the editing operations that call
 them.
 
+@defvar before-change-functions
+This variable holds a list of a functions to call before any buffer
+modification.  Each function gets two arguments, the beginning and end
+of the region that is about to change, represented as integers.  The
+buffer that is about to change is always the current buffer.
+@end defvar
+
+@defvar after-change-functions
+This variable holds a list of a functions to call after any buffer
+modification.  Each function receives three arguments: the beginning and
+end of the region just changed, and the length of the text that existed
+before the change.  (To get the current length, subtract the region
+beginning from the region end.)  All three arguments are integers.  The
+buffer that's about to change is always the current buffer.
+@end defvar
+
 @defvar before-change-function
-If this variable is non-@code{nil}, then it should be a function; the
-function is called before any buffer modification.  Its arguments are
-the beginning and end of the region that is about to change,
-represented as integers.  The buffer that is about to change is always
-the current buffer.
+This variable holds one function to call before any buffer modification
+(or @code{nil} for no function).  It is called just like the functions
+in @code{before-change-functions}.
 @end defvar
 
 @defvar after-change-function
-If this variable is non-@code{nil}, then it should be a function; the
-function is called after any buffer modification.  It receives three
-arguments: the beginning and end of the region just changed, and the
-length of the text that existed before the change.  (To get the
-current length, subtract the region beginning from the region end.)
-All three arguments are integers.  The buffer that's about to change
-is always the current buffer.
+This variable holds one function to call after any buffer modification
+(or @code{nil} for no function).  It is called just like the functions in
+@code{after-change-functions}.
 @end defvar
 
-Both of these variables are temporarily bound to @code{nil} during the
-time that either of these hooks is running.  This means that if one of
+The four variables above are temporarily bound to @code{nil} during the
+time that any of these functions is running.  This means that if one of
 these functions changes the buffer, that change won't run these
-functions.  If you do want the hook function to run recursively,
-design your hook functions to bind these variables back to their usual
+functions.  If you do want a hook function to make changes that run
+these functions, make it bind these variables back to their usual
 values.
 
 @defvar first-change-hook