Problem: tests: two edit tests change v:testing from 1 to 0.
Solution: Don't change v:testing in these two tests, since it's already
set to 1 in runtest.vim (zeertzjq).
closes: #17660
Signed-off-by: zeertzjq <zeertzjq@outlook.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
" Prepare for calling test_garbagecollect_now().
+" Also avois some delays in Insert mode completion.
let v:testing = 1
" By default, copy each buffer line into allocated memory, so that valgrind can
%d
call setline(1, 'A')
call cursor(1, 1)
- let v:testing = 1
try
call feedkeys("A\<c-x>\<c-k>\<esc>", 'tnix')
catch
- " error sleeps 2 seconds, when v:testing is not set
- let v:testing = 0
endtry
call test_override("char_avail", 1)
%d
call setline(1, 'mad')
call cursor(1, 1)
- let v:testing = 1
try
call feedkeys("A\<c-x>\<c-t>\<esc>", 'tnix')
catch
- " error sleeps 2 seconds, when v:testing is not set
- let v:testing = 0
endtry
call assert_equal(['mad'], getline(1, '$'))
bw!
static int included_patches[] =
{ /* Add new patch number below this line */
+/**/
+ 1511,
/**/
1510,
/**/