turbo-editors/turbo-corepublic Fork 0
v0.9.0
Commits
Clone
git clone https://git.rickub.com/turbo-editors/turbo-core.git
git clone ssh://git@rickub.com/turbo-editors/turbo-core.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

🛟 Updated. 28d5985 · on v0.9.0 · k33g · 10h ago
2026-09-03-third-editor.md · 49 lines · 2.4 KBmarkdown
Blame HistoryOpen raw

Handoff — 2026-09-03 — a third editor joined the family

Where this stopped

Done, nothing in flight. The library was not changed: turbo-python was built against
published v0.4.0 and needed nothing new from here, so no release is required.

What changed, and why

Only claims that count the editors, plus one comment:

README.md (the list), docs/{en,fr}/README.md (the counting sentence),
profile/profile.go (package comment), docs/{en,fr}/how-to/release-the-library.md,
docs/{en,fr}/how-to/write-the-starter-files.md,
docs/{en,fr}/explanation/architecture.md, .memory/summary.md.

docs/{en,fr}/how-to/test-without-publishing.md got more than a count: the workspace now
lists four modules, and a new paragraph says to list nested modules in the use block —
a go.mod under a listed module stops being a module at all, and the error
(directory prefix . does not contain modules listed in go.work) names the wrong problem.

History was left alone on purpose. "tools.DefaultMenu was correct for a year and wrong
the moment there were two editors" is a true sentence about the past.

The sweep, and its result

grep -rnE '"[^"]*\b(Go|Rust|golang|cargo|gopls|rust-analyzer)\b[^"]*"' --include='*.go',
run because a third editor is what exposes a hardcoded language name. Nothing to fix.
Every hit was one of: a false positive ("Go to definition", "Ctrl-G Go to line"), a
doc-comment example of the seam, or a true statement about the implementation
("written in Go." — every editor in this family is written in Go). The About box's
language had already been moved into the profile after Turbo Rust exposed it; a pty run of
turbo-python confirms it now reads "A Turbo C-style editor for Python".

Re-run that sweep the next time an editor is added. It is only worth running if you read
every hit.

Trap for the next session

A pty run of an editor is what finds this library's stale claims about its own menus.
Adding the Code menu made the tutorial and the menus reference wrong in both existing
editors — the bar listing and the "press → four times" count — and no test in any of the
four repositories could see it. Fixed in turbo-go and turbo-rust the same day; if you add a
menu here, re-count the arrows in every editor's tutorial.

State

Suite green, quality gate PASS (0/0/0, complexity 1810, unchanged). Not committed — the
changes are in the working tree on main at 14aae7c.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# Handoff — 2026-09-03 — a third editor joined the family

## Where this stopped

Done, nothing in flight. **The library was not changed**: turbo-python was built against
published `v0.4.0` and needed nothing new from here, so **no release is required**.

## What changed, and why

Only claims that count the editors, plus one comment:

`README.md` (the list), `docs/{en,fr}/README.md` (the counting sentence),
`profile/profile.go` (package comment), `docs/{en,fr}/how-to/release-the-library.md`,
`docs/{en,fr}/how-to/write-the-starter-files.md`,
`docs/{en,fr}/explanation/architecture.md`, `.memory/summary.md`.

`docs/{en,fr}/how-to/test-without-publishing.md` got more than a count: the workspace now
lists four modules, and a new paragraph says to list **nested** modules in the `use` block —
a `go.mod` under a listed module stops being a module at all, and the error
(*directory prefix . does not contain modules listed in go.work*) names the wrong problem.

**History was left alone on purpose.** "`tools.DefaultMenu` was correct for a year and wrong
the moment there were two editors" is a true sentence about the past.

## The sweep, and its result

`grep -rnE '"[^"]*\b(Go|Rust|golang|cargo|gopls|rust-analyzer)\b[^"]*"' --include='*.go'`,
run because a third editor is what exposes a hardcoded language name. **Nothing to fix.**
Every hit was one of: a false positive (`"Go to definition"`, `"Ctrl-G Go to line"`), a
doc-comment example of the seam, or a true statement about the implementation
(`"written in Go."` — every editor in this family *is* written in Go). The About box's
language had already been moved into the profile after Turbo Rust exposed it; a pty run of
turbo-python confirms it now reads "A Turbo C-style editor for Python".

Re-run that sweep the next time an editor is added. It is only worth running if you read
every hit.

## Trap for the next session

**A pty run of an editor is what finds this library's stale claims about its own menus.**
Adding the Code menu made the tutorial and the menus reference wrong in *both* existing
editors — the bar listing and the "press → four times" count — and no test in any of the
four repositories could see it. Fixed in turbo-go and turbo-rust the same day; if you add a
menu here, re-count the arrows in every editor's tutorial.

## State

Suite green, quality gate PASS (0/0/0, complexity 1810, unchanged). **Not committed** — the
changes are in the working tree on `main` at `14aae7c`.