docs: generalize the ambiguous-theme-mapping wording - #7
Merged
Conversation
The v1.3.0 changelog bullet and the matching paragraph in the Theming
section both explained why a template exists by singling out one shipped
Omarchy theme by name and addressing the reader in the second person
("You decide the ambiguous mappings", "fixes it, for your themes,
permanently"). On a public project that reads as pointed at a particular
theme and its author rather than as documentation.
Both passages now state the same case generically -- some palettes
define their `yellow` as a green, which leaves exit-node markers nearly
indistinguishable from the online color -- and keep the concrete fix
(`warning = "{{ orange }}"`), which is the part a reader actually needs.
No behavior, mapping rule, or template change; wording only.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Phundahl
added a commit
that referenced
this pull request
Aug 24, 2026
Records the README wording change from PR #7 in the phase log, along with the rule it sets: public-facing docs describe the class of problem, not a named third-party theme that fails at it, while internal notes may stay specific -- the Phase 30 entry keeps its concrete reference on purpose, since the mapping decision it records only makes sense against the concrete case. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Two README passages explained why the
tailtui.tomltemplate exists by singling out one shipped Omarchy theme by name, and by addressing the reader in the second person:osaka-jadedefines itsyellowas a green …"warning = "{{ orange }}") fixes it, for your themes, permanently."On a public project that reads as pointed at a particular theme and its author, rather than as documentation of a general problem.
What changed
Both passages now state the same case generically — some palettes define their
yellowas a green, which leaves exit-node markers nearly indistinguishable from the online color — while keeping the concrete fix (warning = "{{ orange }}"), which is the part a reader actually needs in order to write their own template.No behavior, mapping rule, or template change. Wording only, so no version bump — nothing user-facing changed in the program itself.
osaka-jadestill appears inCLAUDE.md's Phase 30 entry, which is internal project notes rather than public-facing prose, and is left as-is.🤖 Generated with Claude Code
https://claude.ai/code/session_01RwiJYemgAJhWgsymHTsfn7