zeertzjq bdde07f60e vim-patch:9.0.0533: the win_line() function is much too long ...

Problem:    The win_line() function is much too long.
Solution:   Move code to separate functions.

e49f9acecc

Co-authored-by: Bram Moolenaar <Bram@vim.org>

2023-03-03 19:28:56 +08:00

..

cjson

fix: Add missing void as function argument (#22317)

2023-02-18 21:35:27 +01:00

klib

refactor: replace char_u with char

2022-11-26 15:52:21 +01:00

man

feat(lua): send "--" literally to Lua "-l" script

2023-01-05 17:10:02 +01:00

mpack

fix(tests): fixes for using vim.mpack and more ASAN

2023-02-10 20:19:04 +01:00

nvim

vim-patch:9.0.0533: the win_line() function is much too long

2023-03-03 19:28:56 +08:00

unicode

docs: fix/remove invalid URLs #20647

2022-10-14 08:01:13 -07:00

xdiff

refactor: remove PVS comment on top of files

2021-10-01 21:08:53 +02:00

.asan-blacklist

…

.valgrind.supp

…

bit.c

feat(lua): make sure require'bit' always works, even with PUC lua 5.1

2023-02-22 22:15:19 +01:00

bit.h

feat(lua): make sure require'bit' always works, even with PUC lua 5.1

2023-02-22 22:15:19 +01:00

clint.py

build(lint): remove clint.py rules for braces #20880

2022-11-01 07:39:49 -07:00

coverity-model.c

ci(coverity): model our allocation functions

2022-05-20 08:14:20 -04:00

uncrustify.cfg

build(lint): remove clint.py rules for braces #20880

2022-11-01 07:39:49 -07:00