Commit 8d80ef01 authored by Paul Eggert's avatar Paul Eggert

doc: Use clearer notations for permissions.

* doc/lispref/files.texi (File Attributes, Changing Files):
Use a more-natural notation for octal numbers.
* doc/misc/gnus.texi (Mail Source Customization, Mail Back End Variables):
Use octal notation for file permissions, which are normally
thought of in octal.
(Mail Back End Variables): Use more-plausible modes in example.
parent 51281b32
2011-12-28 Paul Eggert <eggert@cs.ucla.edu>
* files.texi (File Attributes, Changing Files):
Use a more-natural notation for octal numbers.
2011-12-23 Juanma Barranquero <lekktu@gmail.com> 2011-12-23 Juanma Barranquero <lekktu@gmail.com>
* variables.texi (Variables with Restricted Values): * variables.texi (Variables with Restricted Values):
......
...@@ -1115,15 +1115,10 @@ This function recursively follows symbolic links at all levels. ...@@ -1115,15 +1115,10 @@ This function recursively follows symbolic links at all levels.
@end group @end group
@group @group
(set-file-modes "~/junk/diffs" 438) (set-file-modes "~/junk/diffs" #o666)
@result{} nil @result{} nil
@end group @end group
@group
(format "%o" 438)
@result{} "666" ; @r{Convert to octal.}
@end group
@group @group
% ls -l diffs % ls -l diffs
-rw-rw-rw- 1 lewis 0 3063 Oct 30 16:00 diffs -rw-rw-rw- 1 lewis 0 3063 Oct 30 16:00 diffs
...@@ -1570,10 +1565,10 @@ the bitwise complement of the ``umask'' value. ...@@ -1570,10 +1565,10 @@ the bitwise complement of the ``umask'' value.
The argument @var{mode} must be an integer. On most systems, only the The argument @var{mode} must be an integer. On most systems, only the
low 9 bits of @var{mode} are meaningful. You can use the Lisp construct low 9 bits of @var{mode} are meaningful. You can use the Lisp construct
for octal character codes to enter @var{mode}; for example, for octal numbers to enter @var{mode}; for example,
@example @example
(set-default-file-modes ?\644) (set-default-file-modes #o644)
@end example @end example
Saving a modified version of an existing file does not count as creating Saving a modified version of an existing file does not count as creating
......
2011-12-28 Paul Eggert <eggert@cs.ucla.edu>
* gnus.texi (Mail Source Customization, Mail Back End Variables):
Use octal notation for file permissions, which are normally
thought of in octal.
(Mail Back End Variables): Use more-plausible modes in example.
2011-12-20 Alan Mackenzie <acm@muc.de> 2011-12-20 Alan Mackenzie <acm@muc.de>
* cc-mode.texi: Update version string 5.31 -> 5.32. * cc-mode.texi: Update version string 5.31 -> 5.32.
......
...@@ -15033,7 +15033,7 @@ number. ...@@ -15033,7 +15033,7 @@ number.
@item mail-source-default-file-modes @item mail-source-default-file-modes
@vindex mail-source-default-file-modes @vindex mail-source-default-file-modes
All new mail files will get this file mode. The default is 384. All new mail files will get this file mode. The default is @code{#o600}.
@item mail-source-movemail-program @item mail-source-movemail-program
@vindex mail-source-movemail-program @vindex mail-source-movemail-program
...@@ -15123,10 +15123,10 @@ default file modes the new mail files get: ...@@ -15123,10 +15123,10 @@ default file modes the new mail files get:
@lisp @lisp
(add-hook 'nnmail-pre-get-new-mail-hook (add-hook 'nnmail-pre-get-new-mail-hook
(lambda () (set-default-file-modes 511))) (lambda () (set-default-file-modes #o700)))
(add-hook 'nnmail-post-get-new-mail-hook (add-hook 'nnmail-post-get-new-mail-hook
(lambda () (set-default-file-modes 551))) (lambda () (set-default-file-modes #o775)))
@end lisp @end lisp
@item nnmail-use-long-file-names @item nnmail-use-long-file-names
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment