From d4106f6df335b9609939d11289dd9faae2c85bb6 Mon Sep 17 00:00:00 2001 From: ZyX Date: Sat, 6 Feb 2016 21:03:33 +0300 Subject: shada: Make sure that NIL and EXT values can also be parsed back MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- src/nvim/shada.c | 6 ------ 1 file changed, 6 deletions(-) (limited to 'src/nvim/shada.c') 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); -- cgit