rneovim.git/src/nvim, branch fix_semantic_tokens_pull Neovim fork with Rahm's personal hacks. refactor(highlight_group.c): reduce scope of locals 2023-01-19T15:54:59+00:00 Lewis Russell lewis6991@gmail.com 2023-01-19T15:54:59+00:00 5f3b76d5cec27181770c2fff33ea417eee275172 






refactor: replace char_u with char 25 (#21838)
2023-01-19T14:25:56+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-01-19T14:25:56+00:00

4c531714ff24d82bf1a85decf0e0c63c5785e686

refactor: replace char_u with char

Work on https://github.com/neovim/neovim/issues/459




refactor: replace char_u with char

Work on https://github.com/neovim/neovim/issues/459






fix: pass value instead of pointer to isalpha (#21898)
2023-01-19T10:48:49+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-01-19T10:48:49+00:00

363d153bb94a965ff811d8c7514047264b37d61d












vim-patch:8.2.4655: cmdline completion popup menu positioned wrong (#21894)
2023-01-19T07:13:27+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-19T07:13:27+00:00

6e3890f4ce002ba308c09166b00e8ee86b6efa03

Problem:    Command line completion popup menu positioned wrong when using a
            terminal window.
Solution:   Position the popup menu differently when editing the command line.
            (Yegappan Lakshmanan, closes vim/vim#10050, closes vim/vim#10035)

https://github.com/vim/vim/commit/1104a6d0c2004d39e9b6cb8f804d12b628a69869

The test in the patch looks a bit hard to understand.
Add a Lua test that is more straightforward.

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>




Problem:    Command line completion popup menu positioned wrong when using a
            terminal window.
Solution:   Position the popup menu differently when editing the command line.
            (Yegappan Lakshmanan, closes vim/vim#10050, closes vim/vim#10035)

https://github.com/vim/vim/commit/1104a6d0c2004d39e9b6cb8f804d12b628a69869

The test in the patch looks a bit hard to understand.
Add a Lua test that is more straightforward.

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>






refactor(eval.c): factor out get_number_tv() (#21893)
2023-01-19T05:27:36+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-19T05:27:36+00:00

93adf74a03f6fd2d34bdea7cec1c1f120d6643a2

It was refactored into a separate function in Vim in patch 8.2.0149.




It was refactored into a separate function in Vim in patch 8.2.0149.






fix(statusline): don't leak memory with truncated click labels
2023-01-19T02:36:29+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-18T11:10:58+00:00

01ddc097474627f35cc34fb7015dd26505e2ddcc












fix(statusline): don't leak memory with zero-width click labels
2023-01-19T02:36:29+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-18T07:12:45+00:00

295a264b65bd072bf858496e0e5de83d5b1f5ffa

A zero-width click label isn't assigned to any click definition, so its
function name should be freed when filling click definitions.





A zero-width click label isn't assigned to any click definition, so its
function name should be freed when filling click definitions.







vim-patch:9.0.1221: code is indented more than necessary (#21891)
2023-01-19T01:51:59+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-19T01:51:59+00:00

45dc0f3454d826c42efdcd841953b5e7e613bc5e

Problem:    Code is indented more than necessary.
Solution:   Use an early return where it makes sense. (Yegappan Lakshmanan,
            closes vim/vim#11833)

https://github.com/vim/vim/commit/f97a295ccaa9803367f3714cdefce4e2283c771d

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>




Problem:    Code is indented more than necessary.
Solution:   Use an early return where it makes sense. (Yegappan Lakshmanan,
            closes vim/vim#11833)

https://github.com/vim/vim/commit/f97a295ccaa9803367f3714cdefce4e2283c771d

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>






vim-patch:8.2.1698: cannot lock a variable in legacy Vim script like in Vim9 (#21883)
2023-01-19T00:03:13+00:00

zeertzjq
zeertzjq@outlook.com

2023-01-19T00:03:13+00:00

f8669e8a181abad98229d97439a9cafe8c32fc06

Problem:    Cannot lock a variable in legacy Vim script like in Vim9.
Solution:   Make ":lockvar 0" work.

https://github.com/vim/vim/commit/a187c43cfe8863d48b2159d695fedcb71f8525c1

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




Problem:    Cannot lock a variable in legacy Vim script like in Vim9.
Solution:   Make ":lockvar 0" work.

https://github.com/vim/vim/commit/a187c43cfe8863d48b2159d695fedcb71f8525c1

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






ci: enable CI_BUILD on windows (#21557)
2023-01-18T19:23:46+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-01-18T19:23:46+00:00

42d5142367c375be5cbdfbf11d150a5ebe8c30d6

This will ensure warnings are treated as errors when using MSVC.

Also fix const correctness warnings. The warnings in mbyte.c are false
positives that triggers this warning on MSVC v19.32 and lower, which our
CI still use. The (void *) casts can be removed once the CI MSVC version
has been upgraded to v19.33 or higher.




This will ensure warnings are treated as errors when using MSVC.

Also fix const correctness warnings. The warnings in mbyte.c are false
positives that triggers this warning on MSVC v19.32 and lower, which our
CI still use. The (void *) casts can be removed once the CI MSVC version
has been upgraded to v19.33 or higher.