zeertzjq a0b912c6ec vim-patch:8.1.2048: not clear why SafeState and SafeStateAgain are not triggered ...

Problem:    Not clear why SafeState and SafeStateAgain are not triggered.
Solution:   Add log statements.

37d1807a80

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

2023-08-21 14:16:16 +08:00

..

cjson

fix(vim.json)!: remove global options, "null", "array_mt" #24070

2023-06-21 01:10:32 -07:00

klib

refactor(map): avoid duplicated khash_t types for values

2023-05-17 12:26:21 +02:00

man

docs #22363

2023-06-19 02:24:44 -07:00

mpack

fix(build): distinguish vim.mpack from global require'mpack'

2023-04-20 19:00:38 +02:00

nvim

vim-patch:8.1.2048: not clear why SafeState and SafeStateAgain are not triggered

2023-08-21 14:16:16 +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

.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

refactor(map): avoid duplicated khash_t types for values

2023-05-17 12:26:21 +02:00

coverity-model.c

ci(coverity): model our allocation functions

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

nlua0.c

refactor(build): include lpeg as a library

2023-04-27 11:40:00 +02:00

uncrustify.cfg

fix(api): use text_locked() to check textlock

2023-07-05 08:31:52 +01:00