From 1ca89a60d8b5027f7d4491d9da749c2184194f27 Mon Sep 17 00:00:00 2001 From: Jan Edmund Lazo Date: Wed, 12 May 2021 02:50:51 -0400 Subject: vim-patch:8.2.2359: strange test failure with MS-Windows Problem: Strange test failure with MS-Windows. Solution: Skip the system() call for now. https://github.com/vim/vim/commit/e2924328c165f1fc549f91bf212c93c87bb1d9ed --- src/nvim/testdir/test_autocmd.vim | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'src') diff --git a/src/nvim/testdir/test_autocmd.vim b/src/nvim/testdir/test_autocmd.vim index a2aa1c32c5..c2abf71a95 100644 --- a/src/nvim/testdir/test_autocmd.vim +++ b/src/nvim/testdir/test_autocmd.vim @@ -455,6 +455,14 @@ 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 -- cgit