Repository navigation
text: no em dashes in code, output or the registry - #81
Merged
Merged
Conversation
Every em dash outside the docs is gone from the Rust sources, CLI output,
inbox pages, MCP instructions and tool texts, providers.json and the
scripts. Each sentence is rewritten to read without one: a period, a
comma, or "because", "so" or "and" where that is the relation.
The insecure-file stash warning now reads "WARNING, using", so the sed
filters in leak-test.sh and agent-conformance.sh match the new text.
envcrawl problems read "<path> is ...". SHIPPED_SECTIONS in init.rs keeps
its bytes, because undo recognizes those AGENTS.md sections by exact
match; the dashes there are spelled as "\u{2014}" escapes in concat!.
Co-Authored-By: Claude <noreply@anthropic.com>
The insecure-file stash warning reads "tokenstash: WARNING: using insecure-file stash", and the sed filters in leak-test.sh and agent-conformance.sh match it. init's "left <file> untouched" line ends with a period before the error. The errors that reach it start with a path, "writing", "refusing to write" or an OS message, so a period reads right for all of them where "because" does not. Co-Authored-By: Claude <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
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.
Removes every em dash from the code, CLI output, inbox pages, MCP texts, the provider registry and the scripts. The docs, README, changelog, SECURITY, CONTRIBUTING and issue templates are left out because another PR covers them. Each sentence is rewritten to read without the dash: a period where two thoughts meet, a comma for an aside or a list, or "because", "so" or "and" where that is the real relation.
Count. 303 em dashes in 40 files. 294 are rewritten. The other 9 sit in
SHIPPED_SECTIONSincrates/cli/src/cmd/init.rs. Undo matches those AGENTS.md sections byte for byte against what earlier releases wrote, so their text can't change. They are now written as"\u{2014}"escapes insideconcat!, with the same bytes, and I checked them againstmain. After this PR,git grep "—"finds nothing outside the excluded docs.User-visible strings that changed
trust add,workspaces,rotate,report-bad,answer,doctor,ask/tasksstatus lines,run, the multi-key summary fromneed, the port-squatter messages, theinbox_linksdeprecation note,export/importprompts and table notes, andinit's failure lines, which now readleft <file> untouched. <error>.import --from-envscan notes now read<path> is not owned by you, skippedand so on.instructions, thehuman_requestandsecrets_report_invaliddescriptions, and severalnexttexts.providers.json: the OpenAI "Copy it" step and the five "Generated locally" steps.tokenstash: WARNING: using insecure-file stash .... The gitignore comment tokenstash adds now reads# added by tokenstash. Never commit injected secrets.Coverage is decided by the rule line, not the comment, so existing repos are unaffected.Tests and scripts updated to match
scripts/leak-test.shandscripts/agent-conformance.shhadsedfilters keyed on the old stash warning. Both now match the new text.returned to the agent word for word,as the reason if you press Can't do this) still matches.Checks run.
cargo fmt --all -- --check(formatting is disabled repo-wide),cargo clippy --workspace --all-targets --locked -- -D warnings,cargo test --workspace --locked,bash scripts/leak-test.sh,bash -non the changed scripts, andnode --checkon the launcher. All pass.Edits stay on the lines that held a dash, so this should rebase cleanly over the open work in
inbox.rs,notify.rs, the test helpers and the two scripts. The one exception is the opening line of eachSHIPPED_SECTIONSentry, which gainedconcat!(.🤖 Generated with Claude Code
This text cleanup appears safe to merge.
What we checked:
gitignore_coversskips comments and reads the unchanged rule line. Git still checks whether the file is ignored before the secret is written.Summary
Removes literal em dashes from comments, CLI messages, inbox pages, MCP text, provider steps, and scripts.
krishhggintentionally preserves historicalSHIPPED_SECTIONSbytes through Unicode escapes so undo still recognizes older files. Documentation is intentionally left for another PR.Reviews (1) · Last reviewed commit: "text: a colon after WARNING, and init's ..."