From e1dc9ed4641953977028650d8b7300a8680bdf55 Mon Sep 17 00:00:00 2001 From: ZyX Date: Sun, 23 Aug 2015 18:10:40 +0300 Subject: 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. --- runtime/doc/starting.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'runtime') 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. -- cgit