view src/testdir/test_terminal_fail.vim @ 12505:5cf248ecb6e3 v8.0.1131

patch 8.0.1131: not easy to trigger an autocommand for new terminal window commit https://github.com/vim/vim/commit/b00fdf6eed5fec589a86655249a851c2d9ba3bb8 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Sep 21 22:16:21 2017 +0200 patch 8.0.1131: not easy to trigger an autocommand for new terminal window Problem: It is not easy to trigger an autocommand for new terminal window. (Marco Restelli) Solution: Trigger BufWinEnter after setting 'buftype'.
author Christian Brabandt <cb@256bit.org>
date Thu, 21 Sep 2017 22:30:04 +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