That column of numbers running down the left edge of a note editor immediately reads as "code." It eats a bit of horizontal space, and it makes the page feel a little less like blank paper. So what does an ordinary person actually get out of line numbers when writing notes?
The answer doesn't show up after the writing is polished. It shows up while the content is still taking shape.
Jotting three to-dos in a meeting, leaving a question mark while reading, catching a stray thought mid-walk—none of this usually gets written top to bottom, title first. People tend to put one line down, keep adding more below it, and only later decide what should be merged, moved, or expanded.
In a long note, you first have to find that one line again
When a note is only a few lines, locating anything is trivial. Once it grows longer, "move that earlier reminder down under the conclusion" needs a reference point.
That's exactly what line numbers provide: a temporary coordinate. They don't decide your headings, lists, or hierarchy for you—they just let you quickly locate a specific line and confirm which sentence you're about to move, copy, or edit. Meeting shorthand can be checked line by line, scattered fragments can be reordered line by line, and a pile of loose thoughts can stay loose until the relationships become clear enough to grow into an outline.
In Abox Note, line numbers serve this "capture first, organize later" process. They don't require every sentence to sit on its own line—people who prefer writing full paragraphs can keep doing that. They simply mean less hunting and guessing for people who work line by line.
Screen wrapping doesn't change where content lives
On a narrow phone screen, one long sentence might visually wrap into two or three rows. Widen the window, and it may collapse back to one. That's just a "soft wrap" adapting to screen width—it doesn't mean the content actually gained extra lines.
Line numbers track the logical lines a writer creates by pressing Enter, not the rows a screen happens to wrap text into at any given moment. So the same piece of content keeps the same positional reference on a phone and on a desktop, without its number drifting every time the screen width, window size, or font size changes.
That distinction also marks the limits of line numbers: they're most useful for quick captures, shorthand, and situations where you're constantly moving and reorganizing sentences. If you're mostly writing continuous long-form prose and rarely handle content line by line, the benefit shrinks considerably.
Line numbers aren't free
Keeping line numbers means accepting that they take up presence. Editing width is precious on a narrow screen, and a column of digits claims part of it; it can also make first-time users assume this is an editor built only for programmers.
For that column of numbers to actually be useful, it has to stay aligned with the body text at all times. When the body scrolls, the numbers have to scroll with it; when a long sentence wraps, a number can only appear at the start of its logical line; when font size changes, both sides still need to keep the same rhythm. Abox Note keeps the body and the line numbers sharing one consistent layout relationship, so the numbers don't drift further from their matching text the further down the page you go. The specific font and line-height math behind this is an implementation detail, but it points to a real requirement: a line number is only useful if it points to the right place.
So line numbers aren't a decoration that makes an editor look more "professional," and they're not something every notes app is obligated to adopt. Abox Note keeps them because it cares about making unformed content actionable: a stray thought can be written down, found precisely, and then moved to a better place.
Structure can wait. Content doesn't have to lose its handle while it does.