From a3468351f6f3ccbc2fb9f4baea11720a5818df27 Mon Sep 17 00:00:00 2001 From: Lars Hansen Date: Wed, 23 Jun 2004 14:37:27 +0000 Subject: [PATCH] (Saving Buffers): Correct description of `write-contents-functions'. --- lispref/files.texi | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/lispref/files.texi b/lispref/files.texi index aa5b0c397b1..63bc4b42673 100644 --- a/lispref/files.texi +++ b/lispref/files.texi @@ -416,11 +416,12 @@ Even though this is not a normal hook, you can use @code{add-hook} and @c Emacs 19 feature @defvar write-contents-functions This works just like @code{write-file-functions}, but it is intended for -hooks that pertain to the contents of the file, as opposed to hooks that -pertain to where the file came from. Such hooks are usually set up by +hooks that pertain to the contents of the buffer, as opposed to hooks that +pertain to the file the buffers visits. Such hooks are usually set up by major modes, as buffer-local bindings for this variable. If any of the -functions in this hook returns non-@code{nil}, @code{write-file-functions} -is not run. +functions in this hook returns non-@code{nil}, the file is considered +already written and the rest are not called and neither are the functions +in @code{write-file-functions}. This variable automatically becomes buffer-local whenever it is set; switching to a new major mode always resets this variable, but -- 2.39.2