runtime(doc): clarify that a umask is applied to mkdir() Commit: https://github.com/vim/vim/commit/0a336ccb57003c44ba303ccc50cf50cb640c2309 Author: Christian Brabandt <c...@256bit.org> Date: Tue Mar 11 21:14:31 2025 +0100
runtime(doc): clarify that a umask is applied to mkdir() fixes: https://github.com/vim/vim/issues/16849 Signed-off-by: Christian Brabandt <c...@256bit.org> diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt index 80b8a9cc4..ec1088933 100644 --- a/runtime/doc/builtin.txt +++ b/runtime/doc/builtin.txt @@ -1,4 +1,4 @@ -*builtin.txt* For Vim version 9.1. Last change: 2025 Feb 23 +*builtin.txt* For Vim version 9.1. Last change: 2025 Mar 11 VIM REFERENCE MANUAL by Bram Moolenaar @@ -7587,9 +7587,8 @@ mkdir({name} [, {flags} [, {prot}]]) *mkdir()* *E739* If {prot} is given it is used to set the protection bits of the new directory. The default is 0o755 (rwxr-xr-x: r/w for the user, readable for others). Use 0o700 to make it - unreadable for others. This is only used for the last part of - {name}. Thus if you create /tmp/foo/bar then /tmp/foo will be - created with 0o755. + unreadable for others. This is used for the newly created + directories. Note an umask is applied to {prot} (on Unix). Example: > :call mkdir($HOME .. "/tmp/foo/bar", "p", 0o700) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/E1ts6Em-004fi7-S6%40256bit.org.