comparison runtime/doc/testing.txt @ 27257:68c33419fdc6 v8.2.4157

patch 8.2.4157: terminal test fails because Windows sets the title Commit: https://github.com/vim/vim/commit/ae1bd87fe84bfb31379bc5da351bca56a3d3b571 Author: ichizok <gclient.gaap@gmail.com> Date: Thu Jan 20 14:57:29 2022 +0000 patch 8.2.4157: terminal test fails because Windows sets the title Problem: Terminal test fails because Windows sets the title. Solution: Add the "vterm_title" testing override and use it in the test. (Ozaki Kiichi, closes #9556)
author Bram Moolenaar <Bram@vim.org>
date Thu, 20 Jan 2022 16:00:07 +0100
parents b19230a8d40a
children 3649b5a6b1b6
comparison
equal deleted inserted replaced
27256:fc12cb6e29b7 27257:68c33419fdc6
206 term_props reset all terminal properties when the version 206 term_props reset all terminal properties when the version
207 string is detected 207 string is detected
208 ui_delay time in msec to use in ui_delay(); overrules a 208 ui_delay time in msec to use in ui_delay(); overrules a
209 wait time of up to 3 seconds for messages 209 wait time of up to 3 seconds for messages
210 uptime overrules sysinfo.uptime 210 uptime overrules sysinfo.uptime
211 vterm_title setting the window title by a job running in a
212 terminal window
211 ALL clear all overrides ({val} is not used) 213 ALL clear all overrides ({val} is not used)
212 214
213 "starting" is to be used when a test should behave like 215 "starting" is to be used when a test should behave like
214 startup was done. Since the tests are run by sourcing a 216 startup was done. Since the tests are run by sourcing a
215 script the "starting" variable is non-zero. This is usually a 217 script the "starting" variable is non-zero. This is usually a