Mercurial > vim
view src/testdir/test_job_fails.vim @ 12936:c53a80f39a52 v8.0.1344
patch 8.0.1344: using 'imactivatefunc' in the GUI does not work
commit https://github.com/vim/vim/commit/2877d334ad1321d1fcd5f903c0493bd0cdd787f8
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 26 14:56:16 2017 +0100
patch 8.0.1344: using 'imactivatefunc' in the GUI does not work
Problem: Using 'imactivatefunc' in the GUI does not work.
Solution: Do not use 'imactivatefunc' and 'imstatusfunc' in the GUI.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 26 Nov 2017 15:00:06 +0100 |
parents | c1347c968d31 |
children | 415185e2c970 |
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 job = job_start('axdfxsdf') if has('unix') call WaitFor({-> job_status(job) == "dead"}) else call WaitFor({-> job_status(job) == "fail"}) endif endif endfunc