rneovim.git/test/functional/lua/range_spec.lua, branch master

fix(range): preserve single-character intersections #41881

2026-09-12T14:28:54+00:00

Problem:
Intersection rejects ranges whose inclusive end equals the other start,
discarding a shared character and even a one-character self-intersection.

Solution:
Use strict comparisons when checking inclusive ends for non-overlap.
Cover two ranges that share a single character.

AI-assisted

fix(range): use the preceding line for inclusive end marks #41880

2026-09-12T14:27:08+00:00

Problem:
Converting an exclusive end at column zero moves to the preceding row
but calculates the inclusive column from the original row's text.

Solution:
Read the preceding line after decrementing the row. Cover adjacent lines
with unequal lengths.

AI-assisted

test: fix wrong order of args to eq(), neq() #41499

2026-08-26T11:18:22+00:00

feat(pos): mutable vim.Pos, vim.Range fields #41318

2026-08-23T11:13:41+00:00

Allow plugins to set the human-readable fields.

test(harness): migrate away from magic globals

2026-07-21T11:22:39+00:00

Problem:
The magic globals `it`, `describe`, etc., are more trouble than they are
worth.

- Hooking into `after_each` requires `getfenv()` hacks.
- They confuse luals/emmylua, because the top-level `.luarc.json` isn't
  merged with `test/.luarc.json` (apparently a luals limitation?)
- They totally defeat discoverability because the user just has to
  "know" about the various magic symbols.

So they harm DX, which means they serve no purpose at all.

Solution:
- Expose the test API from `testutil`, so tests can call `t.it()`,
  `t.describe()`, etc., in the conventional way.
- Drop `getfenv()` hacks.
- Drop the `setfenv()` injection in `load_chunk`.
- Drop `test/_meta.lua`.

refactor(pos,range): extract `vim.pos._util`

2026-05-20T08:23:03+00:00

Problem:
- To share logic, creating a `vim.Range` currently creates two `vim.Pos` values
  as intermediates, which causes unnecessary table allocations.
- `pos.lua` and `range.lua` contain some overlapping logic.

Solution:
Add `vim.pos._util`, a module for handling
positions represented directly by `row` and `col`.

fix(range): handle inclusive/exclusive positions on multibyte characters

2026-05-18T14:19:07+00:00

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

2026-05-08T09:17:00+00:00

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.

feat(vim.pos): accept buf=0 for current buf #39414

2026-04-26T10:34:18+00:00

feat(vim.pos)!: require `buf` param on vim.pos, vim.range #38665

2026-04-06T15:51:36+00:00

Problem: `buf` is optional even though its needed to perform conversions
and the ordering of `(buf, row, col)` is not consistent.

Solution: make `buf` mandatory on `vim.range` and `vim.pos` and enforce
the `buf, row, col` ordering