rneovim.git/src/nvim, branch rahm

Merge remote-tracking branch 'upstream/master' into mix_20240309

2025-02-05T23:09:29+00:00

fix(log): RPC log format #32337

2025-02-05T21:23:33+00:00

Problem:
RPC log messages show `log_notify` function name, which is not useful:

    DBG 2025-02-04T22:28:02.419 ui.37862   log_notify:57: RPC -> 3: [notify]    nvim_ui_set_focus
    DBG 2025-02-04T22:28:02.419 nvim.37863.0 log_notify:57: RPC <- 1: [notify]    nvim_ui_set_focus

Solution:
Call logmsg() directly.

    DBG 2025-02-04T22:42:00.104 ui.40680   RPC: -> 3: [notify]    nvim_ui_attach
    DBG 2025-02-04T22:42:00.104 ui.40680   RPC: -> 3: [notify]    nvim_set_client_info

fix(messages): add a trailing space to inputlist() etc. prompts (#32328)

2025-02-05T03:36:01+00:00

Before #31525 the prompts had a trailing space.
Also add a test for #7857.

vim-patch:9.1.1076: vim_strnchr() is strange and unnecessary (#32327)

2025-02-04T23:06:33+00:00

Problem:  vim_strnchr() is strange and unnecessary (after v9.1.1009)
Solution: Remove vim_strnchr() and use memchr() instead.  Also remove a
          comment referencing an #if that is no longer present.

vim_strnchr() is strange in several ways:
- It's named like vim_strchr(), but unlike vim_strchr() it doesn't
  support finding a multibyte char.
- Its logic is similar to vim_strbyte(), but unlike vim_strbyte() it
  uses char instead of char_u.
- It takes a pointer as its size argument, which isn't convenient for
  all its callers.
- It allows embedded NULs, unlike other "strn*" functions which stop
  when encountering a NUL byte.

In comparison, memchr() also allows embedded NULs, and it converts bytes
in the string to (unsigned char).

closes: vim/vim#16579

https://github.com/vim/vim/commit/34e1e8de91ff4a8922d454e3147ea425784aa0a0

fix(event-loop): process input before events in getchar() (#32322)

2025-02-04T22:48:56+00:00

Follow-up to #27358.

vim-patch:9.1.1027: no sanitize check when running linematch

2025-02-04T00:42:53+00:00

Problem:  no sanitize check when running linematch
Solution: add sanitize check before applying the linematch algorithm,
          similar to diff_find_change() (Jonathon)

closes: vim/vim#16446

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

Co-authored-by: Jonathon

vim-patch:9.1.1023: Coverity complains about dereferencing NULL pointer

2025-02-04T00:42:53+00:00

Problem:  Coverity complains about dereferencing NULL pointer
Solution: Verify curdiff is not null before dereferencing it

closes: vim/vim#16437

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

Co-authored-by: Christian Brabandt

vim-patch:9.1.1022: linematch option value not completed

2025-02-04T00:42:53+00:00

Problem:  linematch option value not completed
          (after v9.1.1009)
Solution: Update diffoption completion values

related: vim/vim#9661
closes: vim/vim#16437

https://github.com/vim/vim/commit/9162e636b31dcac57876cbdec15a683cedd9760e

Co-authored-by: Christian Brabandt

vim-patch:9.1.1009: diff feature can be improved

2025-02-04T00:42:53+00:00

Problem:  diff feature can be improved
Solution: include the linematch diff alignment algorithm
          (Jonathon)

closes: vim/vim#9661

https://github.com/vim/vim/commit/7c7a4e6d1ad50d5b25b42aa2d5a33a8d04a4cc8a

Co-authored-by: Jonathon

vim-patch:9.1.1074: Strange error when heredoc marker starts with "trim" (#32317)

2025-02-03T23:44:41+00:00

Problem:  Strange error when heredoc marker starts with "trim".
Solution: Check for whitespace after "trim" or "eval" (zeertzjq)

For :python3 etc., a heredoc marker that starts with a lower-case letter
is valid, and when it starts with "trim" it works in a script but not in
a function, and this PR makes it works in a function.
For :let, a heredoc marker that starts with a lower-case letter is not
valid, but when it starts with "trim" or "eval" the error can be a bit
confusing in a function, and this PR make it less confusing.

closes: vim/vim#16574

https://github.com/vim/vim/commit/449c2e5454735fe1cfc8c21b2c6880d6bdf4cd6e