aboutsummaryrefslogtreecommitdiff
path: root/runtime
diff options
context:
space:
mode:
authorZyX <kp-pav@yandex.ru>2015-08-23 18:10:40 +0300
committerZyX <kp-pav@yandex.ru>2015-10-08 22:01:03 +0300
commite1dc9ed4641953977028650d8b7300a8680bdf55 (patch)
tree9972721e1511e130eaf01f7c834a8ba69f990007 /runtime
parent6de5900c50c5fc7d8149ff7114d8114357e4e7f9 (diff)
downloadrneovim-e1dc9ed4641953977028650d8b7300a8680bdf55.tar.gz
rneovim-e1dc9ed4641953977028650d8b7300a8680bdf55.tar.bz2
rneovim-e1dc9ed4641953977028650d8b7300a8680bdf55.zip
shada: First write temporary file and only then check any permissions
It is not logical that on UNIX permissions can prevent even writing temporary file, while on other OS it will first write temporary file and then fail during rename.
Diffstat (limited to 'runtime')
-rw-r--r--runtime/doc/starting.txt5
1 files changed, 1 insertions, 4 deletions
diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt
index 03e64db430..0712888284 100644
--- a/runtime/doc/starting.txt
+++ b/runtime/doc/starting.txt
@@ -1121,10 +1121,7 @@ include:
Such errors are listed at |shada-critical-contents-errors|.
- If writing to the temporary file failed: e.g. because of the insufficient
space left.
-- If renaming file failed: e.g. because of insufficient permissions. On Unix
- permissions are checked before trying to create even the temporary file, so
- permission error can only happen if permissions were changed after starting
- to edit the temporary file and before renaming it.
+- If renaming file failed: e.g. because of insufficient permissions.
- If target ShaDa file has different from the Neovim instance's owners (user
and group) and changing them failed. Unix-specific, applies only when
Neovim was launched from root.