When you search a manuscript, what you actually need is not "found it" but "how many". Knowing the count before replacing lets you stop when the number does not match your expectation. Replacing without it means discovering afterwards that you changed too much.
This article covers treating search as a counting tool and what a Mac editor can tell you. The replacement procedure itself is covered separately.
Search has two uses
- Search to arrive — where was that scene? Finding it ends the task
- Search to count — how many occurrences? The count is the answer
Revision and consistency work use the second. Yet most people search with the first mindset and stop at the first hit.
The usual approach
In an editor that does not display a result count, search moves through one match at a time. Establishing the total then means counting those moves manually.
"Press to count" does not last
Manual counting can introduce errors.
If the search wraps to the start or you pause to inspect a passage, you can lose track of where the count stopped. The result may become a vague sense of "quite a few" instead of a checked total.
And "quite a few" cannot support a replacement decision. Thinking there were three and replacing forty is exactly what happens when the count was never established.
The other problem is multiple files. With one file per chapter, you search twenty files and add the totals yourself.
rune Studio returns counts and locations together
rune Studio can search inside a single manuscript and across a whole workspace.
I verified this by driving the development build from the command line. A workspace-wide search returned four files examined and two matches, each with the file name, line number, the text of that line, and its position.
No pressing to count. The number arrives first, and the locations arrive with it.
Regular expressions are supported
You can search for patterns rather than literal text. Searching for a chapter-heading pattern returned three matches, picking up chapters one, two, and three together.
That is what makes it useful for inconsistent spelling — both variants found in one pass.
Search worked in the measured large-file case
The 300,500-character test manuscript was flagged as large, and searching it returned 8,347 matches in 0.08 seconds. This single measurement does not establish an exact activation boundary or guarantee the same speed elsewhere; it records that search returned results in this large-file test.
Half-width characters can be located
There is also a function reporting where half-width alphanumerics and symbols occur. Running it on a manuscript returned six positions with the actual characters.
Useful when normalising alphanumerics in a horizontal practical book, or checking whether full-width and half-width are mixed.
What the count tells you to do
A count is a signal to stop when it differs from your expectation. Even an exact match is not permission to replace immediately. One missed intended occurrence and one unintended match can cancel out, leaving the expected total.
Fewer than expected. The query may be too narrow. Check for spelling variants and an accidentally limited scope, then try a pattern that includes the alternatives.
Exactly as expected. Review the file names, line numbers, and matching lines. If the list is short, inspect every result. If it is long, inspect examples from every file and each distinct context. A matching total does not validate the set.
More than expected. The additional results may be intended occurrences you had forgotten, or unintended matches inside quotations, proper nouns, or homographs. Do not classify the excess automatically. Review the result contexts, then narrow the condition if needed.
Use the count to detect a surprise, then use locations and context to decide the target set. Both stages belong before replacement.
Who this suits, and who is fine without it
It suits people revising long manuscripts. The habit of establishing a count before replacing pays more the longer the work.
Short pieces are fine with pressing next. At three thousand characters you can count.
Scope note: what was verified is workspace-wide search, regular expressions, half-width search, and search speed on a large file.
Summary
- Revision search is for counting, not arriving
- Manual counting in an editor without a displayed count can introduce errors
- rune Studio returns the count together with file names, line numbers, and the text of each line
- An expected count is not proof of safety; review locations and context to validate the target set
- 8,347 matches in 0.08 seconds on a 300,500-character file — counting stays practical
For a first step, search one word you were about to replace. Read the count, then inspect the result lines and confirm that each distinct context really belongs in the replacement set.
See the current product scope on the Rune Studio product page.
