Luis Calle 416f3482e7 fix(vim.range): empty ranges semantics vs regular ranges #39474 ...

Problem:
- Empty ranges have different `<`, `<=`, `has` and `intersect` semantics compared to regular ranges.
- `to_inclusive_pos` assumes that the end position of a range is exclusive, which is not true for empty ranges

Solution:
Special case empty ranges in these operations.

2026-05-08 05:17:00 -04:00

..

nvim

refactor: rename _ensure_integer => _assert_integer

2026-03-13 20:32:01 +01:00

uv

build(deps): bump luv to 1.52.1-0

2026-03-16 10:29:58 +01:00

vim

fix(vim.range): empty ranges semantics vs regular ranges #39474

2026-05-08 05:17:00 -04:00

coxpcall.lua

build: add luals check

2025-02-09 18:10:54 +01:00

editorconfig.lua

build(lint): allow "bufnr" as positional param #39515

2026-04-30 07:12:35 -04:00

man.lua

feat(lua)!: vim.isnil, vim.nonnil, deprecate vim.F #39495

2026-05-06 08:15:00 -04:00