rneovim.git/test/old/testdir/samples, branch fix_20726 Neovim fork with Rahm's personal hacks. vim-patch:9.0.2134: ml_get error when scrolling (#26264) 2023-11-29T05:24:24+00:00 zeertzjq zeertzjq@outlook.com 2023-11-29T05:24:24+00:00 640680cccead28c28b1b789c254fc83d55979c08 Problem: ml_get error when scrolling after delete Solution: mark topline to be validated in main_loop if it is larger than current buffers line count reset_lnums() is called after e.g. TextChanged autocommands and it may accidentally cause curwin->w_topline to become invalid, e.g. if the autocommand has deleted some lines. So verify that curwin->w_topline points to a valid line and if not, mark the window to have w_topline recalculated in main_loop() in update_topline() after reset_lnums() returns. fixes: vim/vim#13568 fixes: vim/vim#13578 https://github.com/vim/vim/commit/c4ffeddfe5bd1824650e9b911ed9245bf56c69e3 The error doesn't happen in Nvim because Nvim triggers TextChanged after calling update_topline(). Co-authored-by: Christian Brabandt <cb@256bit.org> 
Problem:  ml_get error when scrolling after delete
Solution: mark topline to be validated in main_loop
          if it is larger than current buffers line
          count

reset_lnums() is called after e.g. TextChanged autocommands and it may
accidentally cause curwin->w_topline to become invalid, e.g. if the
autocommand has deleted some lines.

So verify that curwin->w_topline points to a valid line and if not, mark
the window to have w_topline recalculated in main_loop() in
update_topline() after reset_lnums() returns.

fixes: vim/vim#13568
fixes: vim/vim#13578

https://github.com/vim/vim/commit/c4ffeddfe5bd1824650e9b911ed9245bf56c69e3

The error doesn't happen in Nvim because Nvim triggers TextChanged after
calling update_topline().

Co-authored-by: Christian Brabandt <cb@256bit.org>
 test(old): move memfile_test.c to test/old/ (#22567) 2023-03-08T02:46:09+00:00 zeertzjq zeertzjq@outlook.com 2023-03-08T02:46:09+00:00 0e7edd70a95d962dfbe5b52c2767887a7131e0a0 






test: move oldtests to test directory (#22536)
2023-03-07T03:13:04+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-03-07T03:13:04+00:00

af23d173883f47fd02a9a380c719e4428370b484

The new oldtest directory is in test/old/testdir. The reason for this is
that many tests have hardcoded the parent directory name to be
'testdir'.




The new oldtest directory is in test/old/testdir. The reason for this is
that many tests have hardcoded the parent directory name to be
'testdir'.