Terminal typography bureau

Iosevka flight check

A typeface can look handsome in a screenshot and still betray you at 2 a.m. Put Iosevka through four practical cockpit tests before granting it terminal clearance.

Begin inspection ↓
font-check.sh
function inspect(glyphs) {
  const suspects = ["0O", "1lI"];
  return glyphs
    .filter(clearAt(13))
    .map(readable => "✓");
}

$ ./font-check.sh
tracking ambiguous glyphs...
terminal clearance: PENDING_
0O 1lI =>
Test protocol

Iosevka is unusually narrow, crisp, and serious about distinguishing look-alike characters. This lab checks the things that matter in actual code: density, ambiguity, operators, and recognition under pressure.

01

Tune the cockpit

Edit real text. Make it tiny. Squeeze the lines. A terminal font earns its keep under imperfect conditions.

02

Interrogate the suspects

Every production incident has a lineup. These are the usual characters of interest.

0Ozero / capital O
slashed versus round
1lIone / lower l / capital I
three distinct silhouettes
{[()]}nested delimiters
open, close, breathe
'"`quote / double / grave
tiny but consequential
,.;:punctuation deck
baseline matters
S5$letter / number / symbol
similar, not identical
rn mthe kerning trap
two letters stay two
@#&terminal wildlife
strange at any size
03

Operator parade

Ligatures can turn character pairs into symbols. Compare the fused display with the literal source underneath.

=> !== <=
=== -> >=
=> !== <=
=== -> >=
04

Glyph gauntlet

Five rapid identifications. The character at the marker is the suspect. Trust your eyes, not your assumptions.

round 0/5score 0time —
READY_
A tiny test of terminal eyesight.
Cleared
Inspection record № 1126

Iosevka is cleared for terminal duty.

Narrow enough for busy panes, deliberate enough for suspicious glyphs, and full of the typographic details nobody notices until they go wrong. A sensible pilot still tests it in their own editor at their own favourite slightly-too-small size.