Mercurial > vim
changeset 23756:65d11d6ed4c2 v8.2.2419
patch 8.2.2419: autocmd test was failing on MS-Windows with GUI
Commit: https://github.com/vim/vim/commit/d697ddea1466d877a79f8c56d46361dc54e9baef
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Jan 28 12:08:35 2021 +0100
patch 8.2.2419: autocmd test was failing on MS-Windows with GUI
Problem: Autocmd test was failing on MS-Windows with GUI.
Solution: Remove stray feedkeys().
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Thu, 28 Jan 2021 12:15:04 +0100 |
| parents | 87ca35959711 |
| children | b873d83d2f87 |
| files | src/testdir/test_autocmd.vim src/version.c |
| diffstat | 2 files changed, 2 insertions(+), 9 deletions(-) [+] |
line wrap: on
line diff
--- a/src/testdir/test_autocmd.vim +++ b/src/testdir/test_autocmd.vim @@ -214,7 +214,6 @@ func Test_autocmd_bufunload_avoiding_SEG normal! i1 call assert_fails('edit a.txt', 'E517:') - call feedkeys("\<CR>") autocmd! test_autocmd_bufunload augroup! test_autocmd_bufunload @@ -503,14 +502,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