Mercurial > vim
view src/testdir/test_terminal_fail.vim @ 33337:19b4f85c2649 v9.0.1932
patch 9.0.1932: Vim9: error when using null object constructor
Commit: https://github.com/vim/vim/commit/7398f367d5125eedfb4058c63a5d167fe8601e3d
Author: Yegappan Lakshmanan <yegappan@yahoo.com>
Date: Sun Sep 24 23:09:10 2023 +0200
patch 9.0.1932: Vim9: error when using null object constructor
Problem: Vim9: error when using null object constructor
Solution: Check for a null object only when calling an object method
closes: #13154
closes: #13163
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 24 Sep 2023 23:15:07 +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