rneovim.git/test/functional/lua/hl_spec.lua, branch rahm Neovim fork with Rahm's personal hacks. test(lua/hl_spec): set timeout for transient state (#32169) 2025-01-23T00:11:53+00:00 zeertzjq zeertzjq@outlook.com 2025-01-23T00:11:53+00:00 fd55c7df6f7eb61c65e93c6dd8beffaeed93d2ed 






feat(lua): vim.hl.range() "timeout" #32012
2025-01-22T15:46:24+00:00

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

2025-01-22T15:46:24+00:00

af0ef2ac9dd19b7c4005a3197334d3e7d554646c

Problem:
`vim.hl.on_yank()` has a "timeout" behavior but this is not available for
`vim.hl.range()`.

Solution:
Add `timeout` arg to `vim.hl.range()`.




Problem:
`vim.hl.on_yank()` has a "timeout" behavior but this is not available for
`vim.hl.range()`.

Solution:
Add `timeout` arg to `vim.hl.range()`.






refactor: use nvim.foo.bar format for namespaces
2025-01-15T03:55:29+00:00

Maria José Solano
majosolano99@gmail.com

2025-01-14T03:39:03+00:00

850084b519e18122820478a71bb4bfa4c15e528a












fix(tests): needing two calls to setup a screen is cringe
2024-11-14T11:40:57+00:00

bfredl
bjorn.linse@gmail.com

2024-11-11T21:15:19+00:00

e61228a214ebda9845db9462dad0a8c362d3963f

Before calling "attach" a screen object is just a dummy container for
(row, col) values whose purpose is to be sent as part of the "attach"
function call anyway.

Just create the screen in an attached state directly. Keep the complete
(row, col, options) config together. It is still completely valid to
later detach and re-attach as needed, including to another session.





Before calling "attach" a screen object is just a dummy container for
(row, col) values whose purpose is to be sent as part of the "attach"
function call anyway.

Just create the screen in an attached state directly. Keep the complete
(row, col, options) config together. It is still completely valid to
later detach and re-attach as needed, including to another session.







refactor: rename vim.highlight => vim.hl
2024-10-20T22:54:43+00:00

Justin M. Keyes
justinkz@gmail.com

2024-10-17T09:16:16+00:00

18b43c331d8a0ed87d7cbefe2a18543b8e4ad360

Problem:
- `vim.highlight` module does not follow `:help dev-name-common`, which
  documents the name for "highlight" as "hl".
- Shorter names are usually preferred.

Solution:
Rename `vim.highlight` to `vim.hl`.

This is not a breaking change until 2.0 (or maybe never).





Problem:
- `vim.highlight` module does not follow `:help dev-name-common`, which
  documents the name for "highlight" as "hl".
- Shorter names are usually preferred.

Solution:
Rename `vim.highlight` to `vim.hl`.

This is not a breaking change until 2.0 (or maybe never).