aboutsummaryrefslogtreecommitdiffstats
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>1994-07-02 04:09:37 +0000
committerRichard M. Stallman <[email protected]>1994-07-02 04:09:37 +0000
commit6ca8823106d9d597914a67ae0216f09a0b7b033c (patch)
treeaaf4b7c658b6b45d7a9e5ff0ff9c77e5c764c68f /lispref
parent1493e1f88846ecb641f3277a9d89118068f33cd6 (diff)
*** empty log message ***
Diffstat (limited to 'lispref')
-rw-r--r--lispref/files.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/lispref/files.texi b/lispref/files.texi
index 48b63f0e91..199f594955 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