Mercurial > vim
view src/testdir/test_terminal_fail.vim @ 14642:96858d612aff v8.1.0334
patch 8.1.0334: 'autowrite' takes effect when buffer is not to be written
commit https://github.com/vim/vim/commit/8c9e7b00f6566dc41e794ef11c93d93b034c7134
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Aug 30 13:07:17 2018 +0200
patch 8.1.0334: 'autowrite' takes effect when buffer is not to be written
Problem: 'autowrite' takes effect when buffer is not to be written.
Solution: Don't write buffers that are not supposed to be written. (Even Q
Jones, closes #3391) Add tests for 'autowrite'.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 30 Aug 2018 13:15:06 +0200 |
parents | e9dbdc4d8279 |
children | f38fcbf343ce |
line wrap: on
line source
" This test is in a separate file, because it usually causes reports for memory " leaks under valgrind. That is because when fork/exec fails memory is not " freed. Since the process exists right away it's not a real leak. if !has('terminal') finish endif source shared.vim func Test_terminal_redir_fails() if has('unix') let buf = term_start('xyzabc', {'err_io': 'file', 'err_name': 'Xfile'}) call term_wait(buf) call WaitFor('len(readfile("Xfile")) > 0') call assert_match('executing job failed', readfile('Xfile')[0]) call WaitFor('!&modified') call delete('Xfile') bwipe endif endfunc