aboutsummaryrefslogtreecommitdiff
path: root/test/functional/shada/helpers.lua
diff options
context:
space:
mode:
authorZyX <kp-pav@yandex.ru>2015-08-08 13:27:55 +0300
committerZyX <kp-pav@yandex.ru>2015-10-08 22:00:29 +0300
commit1542fc221e52f31d5102730a222b5dbbae782dcd (patch)
treea9de4e5f891d3c68da0319f10a02bb744313c401 /test/functional/shada/helpers.lua
parent1e067920994a5dd02df8f71f21afa29f0d4bcd21 (diff)
downloadrneovim-1542fc221e52f31d5102730a222b5dbbae782dcd.tar.gz
rneovim-1542fc221e52f31d5102730a222b5dbbae782dcd.tar.bz2
rneovim-1542fc221e52f31d5102730a222b5dbbae782dcd.zip
shada,functests: Improve detection of invalid ShaDa files
It appears that large portion of non-ShaDa ASCII text files may be parsed as a ShaDa file because it is mostly recognized as a sequence of unknown entries: all ASCII non-control characters are recognized as FIXUINT shada objects, so text like #!/bin/sh powerline "$@" 2>&1 | tee -a powerline (with trailing newline) will be recognized as a correct ShaDa file containing single unknown entry with type 0x23 (dec 35, '#'), timestamp 0x21 (dec 33, '!') and length 0x2F (dec 47, '/') without this commit. With it parsing this entry will fail.
Diffstat (limited to 'test/functional/shada/helpers.lua')
0 files changed, 0 insertions, 0 deletions