Add Line Numbers: Referencing Items in a List

When you actually need it

Item-by-item discussion is the main use. Number the agenda, the action items, or the checklist and anyone can say item 7 is the problem instead of describing it. Meeting minutes, acceptance checklists, and support reply templates all work this way.

Testing and teaching use it too. Numbered reproduction steps let you say the failure happens at step 3, and numbering the source text makes a line-by-line translation review practical. The common thread is that items need to be cited, not just read.

• Agenda items and action points
• Test steps and reproduction paths
• Source and translation compared line by line

How to avoid the usual problems

The format is a number, a period, and a space, starting at 1 and increasing with the current line order. Blank lines are numbered as well, which leaves gaps that look like missing items. Remove empty lines first so the sequence is continuous.

If the text already has numbers, you get two layers, as in 1. 1. Buy milk. Strip the old numbers first. Do not sort or shuffle afterwards: the number is just text and does not travel with its line, so the labels end up attached to the wrong items.

• Delete blank lines so the numbering is continuous
• Strip existing numbers first
• Never sort after numbering

Alternatives and when not to use it

For 1) style or zero-padded 01 and 02, column editing or a regex replace in the editor is more flexible. In Markdown, manual numbers work, but they do not renumber themselves after edits, so an ordered list is less work in the long run.

Do not put line numbers into code. Let the editor display them, because numbers written into the text have to be removed again by whoever copies the snippet, and they go out of sync the moment the code changes. Log analysis, which relies on original line numbers, has the same problem.