aniani/vim
0
0
Fork 1
mirror of https://github.com/vim/vim.git synced 2025-07-04 23:07:33 -04:00
Code

tests: two edit tests change v:testing from 1 to 0

Browse Source 
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.
This commit is contained in:
zeertzjq 2025-07-04 09:48:45 +08:00
parent a494ce1c64
commit 7a6b4f2ef4
2 changed files with 1 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/testdir/runtest.vim
View File

@ -180,6 +180,7 @@ endif
" 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

6
src/testdir/test_edit.vim
View File

@ -709,12 +709,9 @@ func Test_edit_CTRL_K()
%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)
@ -962,12 +959,9 @@ func Test_edit_CTRL_T()
%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!