rneovim.git/test/functional/lua, branch userregs_2 Neovim fork with Rahm's personal hacks. fix(vim.hl): nvim_buf_del_extmark on invalid buffer #33331 2025-04-05T22:56:40+00:00 phanium 91544758+phanen@users.noreply.github.com 2025-04-05T22:56:40+00:00 28e819018520a2300eaeeec6794ffcd614b25dd2 Problem: nvim_buf_del_extmark error if buffer is destroyed before timer stops Solution: check nvim_buf_is_valid. 
Problem:
nvim_buf_del_extmark error if buffer is destroyed before timer stops

Solution:
check nvim_buf_is_valid.
 test(lua/hl_spec): fix hang on exit with ASAN (#33298) 2025-04-04T01:19:13+00:00 zeertzjq zeertzjq@outlook.com 2025-04-04T01:19:13+00:00 4ef9dcb1eb7d969687872699d92e0860f3c9ff3a 






feat(vim.hl): allow multiple timed highlights simultaneously #33283
2025-04-03T14:26:56+00:00

Siddhant Agarwal
68201519+siddhantdev@users.noreply.github.com

2025-04-03T14:26:56+00:00

eae2d3b145c724e8c801c7c22a2ccc3bde5534eb

Problem: Currently vim.hl.range only allows one timed highlight.
Creating another one, removes the old one.

Solution: vim.hl.range now returns a timer and a function. The timer
keeps track of how much time is left in the highlight and the function
allows you to clear it, letting the user decide what to do with old
highlights.




Problem: Currently vim.hl.range only allows one timed highlight.
Creating another one, removes the old one.

Solution: vim.hl.range now returns a timer and a function. The timer
keeps track of how much time is left in the highlight and the function
allows you to clear it, letting the user decide what to do with old
highlights.






test(lua/secure_spec): fix failure with long path (#33280)
2025-04-03T13:32:17+00:00

zeertzjq
zeertzjq@outlook.com

2025-04-03T13:32:17+00:00

974a3aa2c4c34f97ce015466a7dfc5fd727fccc2

Ref #33278




Ref #33278






refactor(diagnostic)!: remove deprecated diagnostic APIs (#33072)
2025-03-26T18:56:23+00:00

Gregory Anders
greg@gpanders.com

2025-03-26T18:56:23+00:00

9acb52c8f386ea0a026ba4e314e1294da66f8e79












fix: temporarily disable 0.12 deprecation tests
2025-03-26T13:49:23+00:00

Justin M. Keyes
justinkz@gmail.com

2025-03-26T13:19:47+00:00

2e68e9c051dcf1a896b19535513f3fd97e68b415

Re-enable these after release.





Re-enable these after release.







fix(lua): no omni/cmdline completion for vim.env (#33044)
2025-03-25T23:35:12+00:00

Phạm Bình An
111893501+brianhuster@users.noreply.github.com

2025-03-25T23:35:12+00:00

6b00c9acfde954a3e992a2932eca9fa5902a1298

Problem:
- `:lua vim.env.<Tab>` does not show completion of environment variables
- Meanwhile, `:let $<Tab>` does show completion of environment variables

Solution:
- Fix it




Problem:
- `:lua vim.env.<Tab>` does not show completion of environment variables
- Meanwhile, `:let $<Tab>` does show completion of environment variables

Solution:
- Fix it






fix(cmdline): cmdline completion of _defer_require() modules #33007
2025-03-24T12:14:22+00:00

phanium
91544758+phanen@users.noreply.github.com

2025-03-24T12:14:22+00:00

af4231d4070c8d664b919f5466a827905881ef32

Problem:
`:lua vim.lsp.c<tab>` does not list vim.lsp.completion in the completion
list after 24cea4c7f7417c7fe99a98a0487f51dd68c4f409.

Solution:
- Always include `vim.lsp._submodule` keys in candidates.
  - Fixes `vim.lsp.c<tab>` -> `vim.lsp.completion`.
- Eager-load `vim.lsp.completion` to get its completion.
  - Fixes `vim.lsp.completion.g<tab>` -> `vim.lsp.completion.get`.




Problem:
`:lua vim.lsp.c<tab>` does not list vim.lsp.completion in the completion
list after 24cea4c7f7417c7fe99a98a0487f51dd68c4f409.

Solution:
- Always include `vim.lsp._submodule` keys in candidates.
  - Fixes `vim.lsp.c<tab>` -> `vim.lsp.completion`.
- Eager-load `vim.lsp.completion` to get its completion.
  - Fixes `vim.lsp.completion.g<tab>` -> `vim.lsp.completion.get`.






test(log): use tempfile for expected error logs #33017
2025-03-23T23:12:50+00:00

luukvbaal
luukvbaal@gmail.com

2025-03-23T23:12:50+00:00

958df63606687fff6f805255ff3848dd34f33082












fix(log): unify error messages for vim.ui_attach/decor providers #33005
2025-03-21T10:05:01+00:00

luukvbaal
luukvbaal@gmail.com

2025-03-21T10:05:01+00:00

c908c2560db891dcd152ed9d3cf10a36179bfed6

Problem:  Error messages that cause a vim.ui_attach() namespace to
          detach are not visible in the message history. Decoration
          provider and vim.ui_attach error messages are dissimilar.
Solution: Emit vim.ui_attach() errors as an actual message in addition
          to logging it. Adjust error message format.




Problem:  Error messages that cause a vim.ui_attach() namespace to
          detach are not visible in the message history. Decoration
          provider and vim.ui_attach error messages are dissimilar.
Solution: Emit vim.ui_attach() errors as an actual message in addition
          to logging it. Adjust error message format.