Patch 9.0.0969
Problem:Matchparen highlight is not updated when switching buffers.
Solution: Listen to the BufLeave and the BufWinEnter autocmd events.
(closes #11626)
Files: runtime/plugin/matchparen.vim, src/testdir/test_display.vim,
src/testdir/dumps/Test_mat
Patch 9.0.0968
Problem:GUI mouse event test is a bit flaky.
Solution: Mark the test case as flaky. Move test function failure checks to
a separate test function.
Files: src/testdir/test_gui.vim
*** ../vim-9.0.0967/src/testdir/test_gui.vim2022-10-04 20:14:23.461997287
Patch 9.0.0967 (after 9.0.0965)
Problem:Leaking memory from autocmd windows.
Solution: Free window when auc_win is not NULL.
Files: src/globals.h, src/autocmd.c, src/window.c, src/quickfix.c,
src/eval.c, src/screen.c
*** ../vim-9.0.0966/src/globals.h 2022-11-28 18:5
Patch 9.0.0966 (after 9.0.0965)
Problem:Some compilers don't allow a declaration after a label.
Solution: Move the declaration to the start of the block. (John Marriott)
Files: src/screen.c
*** ../vim-9.0.0965/src/screen.c2022-11-28 18:51:38.955571567 +
--- src/screen.c
On 29-Nov-2022 05:52, Bram Moolenaar wrote:
Patch 9.0.0965
Problem:Using one window for executing autocommands is insufficient.
Solution: Use up to five windows for executing autocommands.
Files: src/globals.h, src/structs.h, src/autocmd.c,
src/proto/autocmd.pro, src/main
Patch 9.0.0965
Problem:Using one window for executing autocommands is insufficient.
Solution: Use up to five windows for executing autocommands.
Files: src/globals.h, src/structs.h, src/autocmd.c,
src/proto/autocmd.pro, src/main.c, src/eval.c, src/evalwindow.c,
> Personally, I haven't measured a significant difference between prop_add()
> and prop_add_list() for normal text-properties. For signs, on the
> other hand, there's a significant difference between sign_place() in a
> for-loop and sign_place_list().
>
> But what I've noticed is that calling p
Patch 9.0.0964
Problem:Status line of other window not redrawn when dragging it when
'splitkeep' is set to "screen".
Solution: Set w_redr_status earlier. (Luuk van Baal, closes #11635,
closes #11632)
Files: src/window.c, src/testdir/test_window_cmd.vim,
Personally, I haven't measured a significant difference between prop_add()
and
prop_add_list() for normal text-properties. For signs, on the other hand,
there's a significant difference between sign_place() in a for-loop and
sign_place_list().
But what I've noticed is that calling prop_remove() c
Patch 9.0.0963
Problem:Function name does not match autocmd event name.
Solution: Rename "optionsset" to "optionset". (closes #11630)
Files: src/option.c, src/optionstr.c, src/proto/optionstr.pro,
src/testdir/test_quickfix.vim
*** ../vim-9.0.0962/src/option.c2022-
Yegappan wrote:
> > > Currently the prop_add_list() function doesn't support adding multiple
> > > virtual text properties. This functionality is useful when applying
> > > the inlay hints reply received from a LSP server.
> >
> > What is against calling prop_add() for each one?
>
> When addin
> I haven't managed to build Vim from source with if_pyth, but I think this is
> related to these lines in `aucmd_prepbuf()`:
> ```c
> if (win == NULL && aucmd_win_used)
> // Strange recursive autocommand, fall back to using the current
> // window. Expect a few side effects...
12 matches
Mail list logo