Files
neovim/test/functional
Matthew Malcomson 263849b2dd fold: foldMoveRange(): fix :move bug #6534
Closes #6540

In #6221 there was a mistake in calculating which folds need to be
re-ordered. When there are no folds after those that have been adjusted,
then `move_end` remains 0. This results in reverse_fold_order()
swapping folds that have been adjusted with uninitialised folds in the
remainder of the grow array.

Add a check in foldMoveRange() to account for this case.
2017-04-17 04:45:55 +02:00
..
2017-04-09 03:31:13 +03:00
2017-04-11 02:37:39 +02:00
2017-04-09 03:31:13 +03:00
2017-03-29 10:08:45 +03:00
2016-06-10 21:50:49 +03:00