From bcafbc3f7b43ed2b773a539db8f7c0230d712014 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Wed, 12 Mar 2025 06:46:45 +0800 Subject: vim-patch:0a336cc: runtime(doc): clarify that a umask is applied to mkdir() (#32845) fixes: vim/vim#16849 https://github.com/vim/vim/commit/0a336ccb57003c44ba303ccc50cf50cb640c2309 Co-authored-by: Christian Brabandt --- runtime/lua/vim/_meta/vimfn.lua | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'runtime/lua/vim/_meta/vimfn.lua') diff --git a/runtime/lua/vim/_meta/vimfn.lua b/runtime/lua/vim/_meta/vimfn.lua index 5504d577d6..6c2b6af583 100644 --- a/runtime/lua/vim/_meta/vimfn.lua +++ b/runtime/lua/vim/_meta/vimfn.lua @@ -6173,10 +6173,9 @@ function vim.fn.min(expr) end --- 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. ---- ---- {prot} is applied for all parts of {name}. Thus if you create ---- /tmp/foo/bar then /tmp/foo will be created with 0o700. Example: >vim +--- unreadable for others. This is used for the newly created +--- directories. Note an umask is applied to {prot} (on Unix). +--- Example: >vim --- call mkdir($HOME .. "/tmp/foo/bar", "p", 0o700) --- ---