summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2000-03-09 13:59:23 +0000
committerRichard M. Stallman <rms@gnu.org>2000-03-09 13:59:23 +0000
commitf74bbbbf5574dd0be3237a179da1ead133ffc89f (patch)
treea2a64c4a3c505783ab41b879caa83af00792c896 /lispref
parent80460654af8a30ad86faef024caac091db9026a7 (diff)
downloademacs-f74bbbbf5574dd0be3237a179da1ead133ffc89f.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref')
-rw-r--r--lispref/files.texi17
1 files changed, 12 insertions, 5 deletions
diff --git a/lispref/files.texi b/lispref/files.texi
index b313c7f64cc..dd102eb66dc 100644
--- a/lispref/files.texi
+++ b/lispref/files.texi
@@ -1328,15 +1328,22 @@ be an integer). Only the low 12 bits of @var{mode} are used.
@defun set-default-file-modes mode
This function sets the default file protection for new files created by
Emacs and its subprocesses. Every file created with Emacs initially has
-this protection. On Unix and GNU/Linux, the default protection is the
-bitwise complement of the ``umask'' value.
+this protection, or a subset of it (@code{write-region} will not give a
+file execute permission even if the default file protection allows
+execute permission). On Unix and GNU/Linux, the default protection is
+the bitwise complement of the ``umask'' value.
The argument @var{mode} must be an integer. On most systems, only the
-low 9 bits of @var{mode} are meaningful.
+low 9 bits of @var{mode} are meaningful. You can use the Lisp construct
+for octal character codes to enter @var{mode}; for example,
+
+@example
+(set-default-file-modes ?\644)
+@end example
Saving a modified version of an existing file does not count as creating
-the file; it does not change the file's mode, and does not use the
-default file protection.
+the file; it preserves the existing file's mode, whatever that is. So
+the default file protection has no effect.
@end defun
@defun default-file-modes