view src/testdir/test_job_fails.vim @ 10720:44a1661f4cfa v8.0.0250

patch 8.0.0250: virtcol() does not work well for multi-byte characters commit https://github.com/vim/vim/commit/0c0590d9827cb07a33c1552cb3558b94bddcb4dc Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jan 28 13:48:10 2017 +0100 patch 8.0.0250: virtcol() does not work well for multi-byte characters Problem: When virtcol() gets a column that is not the first byte of a multi-byte character the result is unpredictable. (Christian Ludwig) Solution: Correct the column to the first byte of a multi-byte character. Change the utf-8 test to new style.
author Christian Brabandt <cb@256bit.org>
date Sat, 28 Jan 2017 14:00:04 +0100
parents e0b783389bea
children c1347c968d31
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.

source shared.vim

func Test_job_start_fails()
  if has('job')
    let g:job = job_start('axdfxsdf')
    if has('unix')
      call WaitFor('job_status(g:job) == "dead"')
      call assert_equal('dead', job_status(g:job))
    else
      call WaitFor('job_status(g:job) == "fail"')
      call assert_equal('fail', job_status(g:job))
    endif
    unlet g:job
  endif
endfunc