Diagnostics
A server reports problems as it finds them — a syntax error, an unused
variable, a type that doesn’t match — and Helix shows each one as a
diagnostic: an underline on the offending text, a mark in the gutter, and
a count of errors and warnings on the statusline. The stand-in here treats
every TODO as a warning and every FIXME as an error.
Two motions walk through them, and a picker lists them:
]dand[d— the next and previous diagnosticSpace-d— a picker of every diagnostic in the bufferSpace-D— the same, across every buffer the server has open
Both motions select the diagnostic they land on, so the message is easy to
read and d or c act on exactly the flagged text. The picker earns its
place when a project has dozens of problems; for one file the motions are
usually enough.
The buffer below has two problems. Jump to the first with ]d, reach the
second through the picker, then come back with [d.