Mercurial > vim
view src/testdir/test_vim9_fails.vim @ 34094:0b25a862bf0c v9.1.0014
patch 9.1.0014: incorrect use of W_WINROW in edit.c
Commit: https://github.com/vim/vim/commit/b1ed7ec9f7d1a0142d4f1c8c83bab9172bc92c7c
Author: zeertzjq <zeertzjq@outlook.com>
Date: Fri Jan 5 18:11:43 2024 +0100
patch 9.1.0014: incorrect use of W_WINROW in edit.c
Problem: incorrect use of W_WINROW in edit.c
Solution: compare against curwin->w_height instead
Remove incorrect use of W_WINROW
In structs.h it is mentioned that w_wrow is relative to w_winrow, so
using W_WINROW doesn't make sense when comparing with window height.
This change won't lead to any observable behavior change:
The condition intends to check if there are 'scrolloff' lines between
the current cursor when the bottom of the window. When W_WINROW(curwin)
is added to curwin->w_height - 1 - get_scrolloff_value(), the condition
is instead satisfied when the cursor is on some screen line below that
position. However,
- If 'scrolloff' is smaller than half the window height, this condition
can only be satisfied when W_WINROW(curwin) == 0. And if it is not
satisfied, update_topline() does the actual scrolling.
- If 'scrolloff' is larger than half the window height, update_topline()
will put the cursor at the center of the window soon afterwards
anyway, because set_topline() now unsets VALID_TOPLINE flag starting
from https://github.com/vim/vim-history/commit/7db7bb45b0f919ff0615d463ebd4fde881c69d1f.
To put it in another way, https://github.com/vim/vim-history/commit/7db7bb45b0f919ff0615d463ebd4fde881c69d1f
makes the update_topline() just below correct the mistakes made in this
block, so this incorrect use of W_WINROW() no longer affects observable
behavior.
closes: #12331
Signed-off-by: zeertzjq <zeertzjq@outlook.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 05 Jan 2024 18:30:03 +0100 |
parents | 54e36d01847b |
children |
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 " Using "idx" from a legacy global function does not work. " This caused a crash when called from legacy context. " This creates a dict that contains a partial that refers to the dict, causing " valgrind to report "possibly leaked memory". func Test_partial_call_fails() let lines =<< trim END vim9script var l = ['a', 'b', 'c'] def Iter(container: any): any var idx = -1 var obj = {state: container} def g:NextItem__(self: dict<any>): any ++idx return self.state[idx] enddef obj.__next__ = function('g:NextItem__', [obj]) return obj enddef var it = Iter(l) echo it.__next__() END call writefile(lines, 'XpartialCall', 'D') let caught = 'no' try source XpartialCall catch /E1248:/ let caught = 'yes' endtry call assert_equal('yes', caught) delfunc g:NextItem__ endfunc