Mercurial > vim
view src/testdir/test_vim9_fails.vim @ 30134:0211a930d873 v9.0.0403
patch 9.0.0403: 'equalalways' may be off when 'laststatus' is zero
Commit: https://github.com/vim/vim/commit/fd7e60a33ddd83a82da4eb6267f1c12fa926f32b
Author: Luuk van Baal <luukvbaal@gmail.com>
Date: Wed Sep 7 14:42:49 2022 +0100
patch 9.0.0403: 'equalalways' may be off when 'laststatus' is zero
Problem: 'equalalways' may be off when 'laststatus' is zero.
Solution: call last_status() before win_equal(). (Luuk van Baal,
closes #11070)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 07 Sep 2022 15:45:05 +0200 |
parents | b94ef0b282f1 |
children | 54e36d01847b |
line wrap: on
line source
" Test for Vim9 script with failures, causing memory leaks to be reported. " The leaks happen after a fork() and can be ignored. source check.vim def Test_assignment() if !has('channel') CheckFeature channel else var chan1: channel var job1: job var job2: job = job_start('willfail') endif enddef " Unclear why this test causes valgrind to report problems. def Test_job_info_return_type() if !has('job') CheckFeature job else var job: job = job_start(&shell) var jobs = job_info() assert_equal('list<job>', typename(jobs)) assert_equal('dict<any>', typename(job_info(jobs[0]))) job_stop(job) endif enddef