summaryrefslogtreecommitdiff
path: root/lispref/files.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1994-07-02 04:09:37 +0000
committerRichard M. Stallman <rms@gnu.org>1994-07-02 04:09:37 +0000
commited947cae614cf6f4bd1c572a65f2560da62affb2 (patch)
treeced59a64308a6164f6d7f7d0f017a5eb486ae324 /lispref/files.texi
parent79e7907a91a730d1e99354499170ef0d38bf4fc0 (diff)
downloademacs-ed947cae614cf6f4bd1c572a65f2560da62affb2.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref/files.texi')
-rw-r--r--lispref/files.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/lispref/files.texi b/lispref/files.texi
index 48b63f0e918..199f5949553 100644
--- a/lispref/files.texi
+++ b/lispref/files.texi
@@ -1866,6 +1866,11 @@ Here are the operations that a magic file name handler gets to handle:
@code{set-visited-file-modtime}, @code{unhandled-file-name-directory},
@code{verify-visited-file-modtime}, @code{write-region}.
+Handlers for @code{insert-file-contents} typically need to clear the
+buffer's modified flag, with @code{(set-buffer-modified-p nil)}, if the
+@var{visit} argument is non-@code{nil}. This also has the effect of
+unlocking the buffer if it is locked.
+
The handler function must handle all of the above operations, and
possibly others to be added in the future. It need not implement all
these operations itself---when it has nothing special to do for a