IntenseFinance/neovim
3
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-02-25 18:55:25 -06:00
Code Issues Packages Projects Releases Wiki Activity

vim-patch:8.2.2419: autocmd test was failing on MS-Windows with GUI

Browse Source 
Problem:    Autocmd test was failing on MS-Windows with GUI.
Solution:   Remove stray feedkeys().
d697ddea14
This commit is contained in:
Jan Edmund Lazo 2021-05-12 02:51:43 -04:00
parent 1ca89a60d8
commit 3f9fa730ce
No known key found for this signature in database
GPG Key ID: 64915E6E9F735B15
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/nvim/testdir/test_autocmd.vim
View File

@ -190,7 +190,6 @@ func Test_autocmd_bufunload_avoiding_SEGV_02()
normal! i1
call assert_fails('edit a.txt', 'E517:')
call feedkeys("\<CR>")
autocmd! test_autocmd_bufunload
augroup! test_autocmd_bufunload
@ -455,14 +454,6 @@ endfunc
" Using :blast and :ball for many events caused a crash, because b_nwindows was
" not incremented correctly.
func Test_autocmd_blast_badd()
" The system() here causes SetChangeMarks() to fail, when run in the GUI
" under Windows. No idea why. Happens with any external command, not
" related to the actual test.
" TODO: find the cause
if has('win32')
throw 'Skipped: calling system() causes problems'
endif
let content =<< trim [CODE]
au BufNew,BufAdd,BufWinEnter,BufEnter,BufLeave,BufWinLeave,BufUnload,VimEnter foo* blast
edit foo1