IntenseFinance/neovim
3
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-02-25 18:55:25 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify about error in shada (#25594)

Browse Source
This commit is contained in:
sisrfeng 2023-10-11 17:58:07 +08:00 committed by GitHub
parent f79052faef
commit 37da0bc0c6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
runtime/doc/starting.txt
View File

@ -1119,7 +1119,8 @@ any free letter from `a` to `z`) while normally it will create this file,
write to it and then rename `{basename}.tmp.X` to `{basename}`. Such errors write to it and then rename `{basename}.tmp.X` to `{basename}`. Such errors
include: include:
- Errors which make Nvim think that read file is not a ShaDa file at all: - Errors which make Nvim think that the file being read is not a ShaDa
file at all:
non-ShaDa files are not overwritten for safety reasons to avoid accidentally non-ShaDa files are not overwritten for safety reasons to avoid accidentally
destroying an unrelated file. This could happen e.g. when typing "nvim -i destroying an unrelated file. This could happen e.g. when typing "nvim -i
file" in place of "nvim -R file" (yes, somebody did that at least with Vim). file" in place of "nvim -R file" (yes, somebody did that at least with Vim).
@ -1337,10 +1338,13 @@ exactly four MessagePack objects:
reasons, see |shada-compatibility|. reasons, see |shada-compatibility|.
*E575* *E576* *E575* *E576*
Errors in ShaDa file may have two types: E575 used for all “logical” errors Errors in ShaDa file may have two types:
and E576 used for all “critical” errors. Critical errors trigger behaviour 1. E575 for “logical” errors.
described in |shada-error-handling| when writing and skipping the rest of the 2. E576 for “critical” errors.
file when reading and include: When writing, critical errors trigger behaviour described in
|shada-error-handling|.
When reading, critical errors cause the rest of the file to be skipped.
Critical errors include:
*shada-critical-contents-errors* *shada-critical-contents-errors*
- Any of first three MessagePack objects being not an unsigned integer. - Any of first three MessagePack objects being not an unsigned integer.
- Third object requesting amount of bytes greater then bytes left in the ShaDa - Third object requesting amount of bytes greater then bytes left in the ShaDa