Search and highlighting work best as a two-stage editorial method. Stage one uses search to build a candidate list with counts and locations. Stage two evaluates whether highlighting is a useful review cue. Neither stage can decide whether repetition is weak prose, deliberate rhythm, a character's speech pattern, or a clue that must remain.
This distinction is useful when a novel has grown beyond a few chapters. A writer may need to check a renamed character, a habitual filler phrase, and a set of continuity terms without turning all three into one indiscriminate replacement job.
Build three review lanes
Use a duplicate of five chapters, such as chapters/01.md through chapters/05.md. The recorded sample contained 18 matches for the name marker NAME603 and 11 matches for the repetition marker REPEAT603.
Create three lanes in a revision note:
- Names: verify spelling, identity, and point of view.
- Repeated phrases: decide whether proximity weakens the sentence.
- Watch terms: flag continuity details for a later reading pass.
Give every occurrence one status: change, keep, or defer. “Highlighted” is not a fourth status. It only means the occurrence is waiting for a human decision.
Stage one: turn search results into review candidates
First, limit search to the five copied chapters. Search NAME603, record the file distribution and total, and clear the query. Then search REPEAT603 and record that result on a separate line.
Read one sentence before and after every match. Keep a name when it is a deliberate nickname or quoted wording. Keep repetition when it creates cadence. Change it when nearby uses do the same job without adding meaning. Defer it when the chapter's full arc is needed to decide.
If your editor supports named highlight lists, create one with a disposable name such as Novel review — copy and add only the watch terms. Keep the search-and-status note as the authoritative record; the list is only a candidate aid.
After editing, rerun the name and repetition searches separately. A lower count is not automatically better; it must equal the number of approved changes plus the number intentionally retained.
Separate documented behavior from observed operations
In the five-chapter copy, workspace search returned 18 name matches and 11 repeated-term matches in separate queries. This demonstrates that the two editorial passes can be counted independently.
A uniquely named highlight list was then created rather than merely previewed. NAME603 and REPEAT603 were added, the list was activated, and a readback showed both entries and the active list index. After the check, the previous active setting was restored and the temporary list was deleted. A final readback matched the starting settings.
Rune Studio's current Mac documentation describes selection-based matching and named word lists whose entries can be highlighted, with adjustable color and opacity. It notes that registered-word highlighting is disabled for very large files to reduce display load. Those are documented capabilities, not observations of how this five-chapter specimen appeared on screen.
Stage two: evaluate highlighting as a revision aid
The observed operation covers list creation, two entries, activation, and restoration. It does not show how the terms looked on screen. It also does not establish that all 18 and 11 occurrences, or the four deliberate exceptions, received the intended visual treatment. Evaluate the candidate rather than filling that gap with an assumption.
| Item | Pass | Hold or fail | Decision |
|---|---|---|---|
| Search candidates | The 18 and 11 results can be reproduced separately | Scope or totals become mixed | Fix the query and scope |
| List state | Two entries, activation, and restoration can be read back | The prior setting cannot be restored | Do not use it in the live profile |
| On-screen cue | A copy shows only useful review cues | Unobserved, distracting, or suspended | Keep the status note and hold color-dependent use |
| Editorial change | Context supplies a reason to change | Color is the only reason | Mark keep or defer |
This evaluation remains usable when the display is unobserved. The search-and-status note stays authoritative. Adopt highlighting only after it is safe and useful in a duplicate; manage the four deliberate exceptions by written reasons, not by color.
A small editorial example
Suppose the phrase “for a moment” appears twice in one paragraph. The first marks hesitation; the second merely delays the next action. Mark the first keep and the second change. Now suppose a character's surname appears in narration and in a quoted letter using an older spelling. Mark the narration change and the quotation keep.
The value of a highlight list is that both cases remain visible during reading. The value of the status note is that color never becomes a command.
Choosing the right manuscript text editor
Look for scoped search, file-and-line results, named highlight lists, and a clear way to disable a list without changing text. Rune Studio's documented capabilities and the existing search/list operations are evaluation inputs. Its article-specific on-screen result remains unobserved, so color-dependent use stays on hold unless a duplicate proves useful. You can review the product on the Rune Studio website.
The durable method is independent of the app: build candidates first, evaluate highlighting second, and edit only after context review. Start with the two known totals—18 names and 11 repeated terms—and preserve the four deliberate exceptions with explicit reasons.
For current details about the Mac search and highlighting features, visit the Rune Studio product page.
