aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorZyX <kp-pav@yandex.ru>2016-02-06 21:03:33 +0300
committerZyX <kp-pav@yandex.ru>2016-04-18 02:46:34 +0300
commitd4106f6df335b9609939d11289dd9faae2c85bb6 (patch)
treea92f5bd8a65a60ef1c1478bf60d5191fe032e917 /src
parent0aa3e7b7ceb259680f9da31bd247b42cdc934449 (diff)
downloadrneovim-d4106f6df335b9609939d11289dd9faae2c85bb6.tar.gz
rneovim-d4106f6df335b9609939d11289dd9faae2c85bb6.tar.bz2
rneovim-d4106f6df335b9609939d11289dd9faae2c85bb6.zip
shada: Make sure that NIL and EXT values can also be parsed back
Note: currently they are both *dumped*, but parsing them produces an error. This is inappropriate: variables should either be skipped with error message when dumping or should be read back properly. It also appears that I did not have test for “has wrong variable value type” error, so nothing got removed from errors_spec.
Diffstat (limited to 'src')
-rw-r--r--src/nvim/shada.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/nvim/shada.c b/src/nvim/shada.c
index a18fd725d2..84880d1a99 100644
--- a/src/nvim/shada.c
+++ b/src/nvim/shada.c
@@ -3883,12 +3883,6 @@ shada_read_next_item_hist_no_conv:
initial_fpos);
goto shada_read_next_item_error;
}
- if (unpacked.data.via.array.ptr[1].type == MSGPACK_OBJECT_NIL
- || unpacked.data.via.array.ptr[1].type == MSGPACK_OBJECT_EXT) {
- emsgu(_(READERR("variable", "has wrong variable value type")),
- initial_fpos);
- goto shada_read_next_item_error;
- }
entry->data.global_var.name =
xmemdupz(unpacked.data.via.array.ptr[0].via.bin.ptr,
unpacked.data.via.array.ptr[0].via.bin.size);