Mercurial > vim
view src/testdir/test_job_fails.vim @ 22172:1b23391fac7e v8.2.1635
patch 8.2.1635: no digraph for 0x2022 BULLET
Commit: https://github.com/vim/vim/commit/57ad94c5a9ee6f3626e1ec728519a8558a4346c8
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Sep 8 19:06:30 2020 +0200
patch 8.2.1635: no digraph for 0x2022 BULLET
Problem: No digraph for 0x2022 BULLET.
Solution: Use "oo". (Hans Ginzel, closes https://github.com/vim/vim/issues/6904)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 08 Sep 2020 19:15:05 +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 func Test_job_start_fails() CheckFeature job let job = job_start('axdfxsdf') if has('unix') call WaitForAssert({-> assert_equal("dead", job_status(job))}) else call WaitForAssert({-> assert_equal("fail", job_status(job))}) endif endfunc " vim: shiftwidth=2 sts=2 expandtab