miniblog.

← Back to all posts
Feb 15, 2025 at 23:12
In LSP, a position is represented as a line number and a column offset (in Unicode code units): https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position This is pretty elegant. You'll get the correct line regardless of encoding bugs, and the editor already knows the line number so it's cheap to compute.
Specification
This document describes the 3.17.x version of the language server protocol. An implementation for node of the 3.17.x version of the protocol can be found here.

Related Posts

Jul 7, 2026 at 08:53
I asked Hermes Agent to change how it set thread titles, and it patched its own source code! Self modifying code is hard to reason about even in a deterministic environment. I'd already limited Hermes access to the todoist API and web search out of an abundance of caution.
Jul 3, 2026 at 09:10
Language design question: what type should `while True {}` have? Bottom: It doesn't contain any `break` statements. Unit: Treat loops with/without `break` consistently. I already have lints that warn on unreachable code after diverging loops, so the Unit case feels surprising.
Jun 13, 2026 at 09:02
3
I've been impressed with code written by Fable in my testing: Difftastic: found small optimisations in a hot loop I'd already profiled extensively. Helped me prototype Dijkstra to A* too (hard to find a good heuristic). Garden: Found some real bugs in my simplistic typechecker.