Nimblesite / Nimblesite/SharpLsp
native_paths_equal is ASCII-only case-insensitive — NTFS is case-insensitive across Unicode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 5
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 27
Description
From the multi-agent audit (src/vfs.rs native_paths_equal): comparison uses eq_ignore_ascii_case, but NTFS case-insensitivity covers the full Unicode range ($UpCase table). Two spellings of a Cyrillic/Greek/accented path that NTFS treats as the same file will not match, so the VFS misses the open buffer for such paths (silent stale-content degradation, same class as #110).
Proper fix needs the OS's own folding (CompareStringOrdinal(..., bIgnoreCase=TRUE) via a small safe wrapper, or per-component Unicode simple case folding as an approximation). Needs a test with a non-ASCII fixture path either way.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/vfs.rs at native_paths_equal and compare its ASCII-only behavior with NTFS Unicode case-insensitivity. Determine whether to use CompareStringOrdinal through a safe wrapper or per-component Unicode simple case folding, then add a non-ASCII fixture path test. Done means NTFS-equivalent spellings match and the VFS finds the open buffer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100