Mercurial > vim
view src/testdir/test_terminal_fail.vim @ 24634:d3c4ecf67604 v8.2.2856
patch 8.2.2856: get readonly error for device that can't be written to
Commit: https://github.com/vim/vim/commit/50157ef1c2e36d8696e79fd688bdd08312196bc6
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat May 15 23:21:05 2021 +0200
patch 8.2.2856: get readonly error for device that can't be written to
Problem: Get readonly error for device that can't be written to.
Solution: Check for being able to write first. (closes https://github.com/vim/vim/issues/8205)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 15 May 2021 23:30:02 +0200 |
parents | 08940efa6b4e |
children |
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 exits right away it's not a real leak. source check.vim CheckFeature terminal source shared.vim func Test_terminal_redir_fails() CheckUnix let buf = term_start('xyzabc', {'err_io': 'file', 'err_name': 'Xfile'}) call TermWait(buf) call WaitFor('len(readfile("Xfile")) > 0') call assert_match('executing job failed', readfile('Xfile')[0]) call WaitFor('!&modified') call delete('Xfile') bwipe endfunc " vim: shiftwidth=2 sts=2 expandtab