turbo-editors/turbo-python · 2026-09-09-alt-t-fix.md

turbo-editors/turbo-pythonpublic⑂ Fork 0

⑂ v1.0.1

2026-09-09-alt-t-fix.md · 23 lines · 1.7 KBmarkdown    Blame HistoryRaw
📦 Turbo Python   1# Handoff — 2026-09-09 — a wrong hot key, found by the next editor
5Ten documentation files changed, both languages, uncommitted. Nothing else in this repository was touched and its suite was not re-run.
7## What was wrong
9Every page that named the Python menu's hot key said `Alt-T`. The menu is `~P~ython`; it answers to `Alt-P`. `Alt-T` is Turbo Rust's, from `Rus~t~`, and it reached these pages through the mechanical substitution that produced them — the identifiers were all changed and the key was not, because a key is not an identifier. It shipped in `v0.1.0` and `v0.1.1`.
11A second sentence was wrong for the same reason: "`Tools` gets `Alt-T`. `Format` gets `Alt-M`" in `how-to/run-uv-commands.md` was Turbo Rust's arithmetic about which letters are free.
13`explanation/architecture.md` also said "all three editors" in both languages. It is four now.
15## Next steps
17
182. **Copy `TestTheToolsReferenceMatchesTheStarterFile` from turbo-moonbit** (`internal/moonbitlang/templates_test.go`). It reads the tools table out of `docs/{en,fr}/reference/*-tools.md` and holds every row to the file `tools.Create` actually writes, and it checks the menu's hot key by name. It is what would have caught this. Perhaps twenty minutes.
193. While there: this repository's `docs/diagrams/packages.drawio` **is** already held to `go list` by `diagram_test.go`. turbo-go and turbo-rust still are not — that item is from the previous handoff and is still open.
21## Watch out for
23- The previous handoff's finding stands: **turbo-go v0.4.2 and turbo-rust v0.4.2 are tagged releases whose suites fail**, on stale template assertions. `01-release.tag.sh` runs `make check`, so the next tag in either will refuse to be cut.

📦 Turbo Python 6fc62ea k33g 11h ago	1	# Handoff — 2026-09-09 — a wrong hot key, found by the next editor
	2
	3	## State
	4
	5	Ten documentation files changed, both languages, uncommitted. Nothing else in this repository was touched and its suite was not re-run.
	6
	7	## What was wrong
	8
	9	Every page that named the Python menu's hot key said `Alt-T`. The menu is `~P~ython`; it answers to `Alt-P`. `Alt-T` is Turbo Rust's, from `Rus~t~`, and it reached these pages through the mechanical substitution that produced them — the identifiers were all changed and the key was not, because a key is not an identifier. It shipped in `v0.1.0` and `v0.1.1`.
	10
	11	A second sentence was wrong for the same reason: "`Tools` gets `Alt-T`. `Format` gets `Alt-M`" in `how-to/run-uv-commands.md` was Turbo Rust's arithmetic about which letters are free.
	12
	13	`explanation/architecture.md` also said "all three editors" in both languages. It is four now.
	14
	15	## Next steps
	16
	17	1. Commit.
	18	2. Copy `TestTheToolsReferenceMatchesTheStarterFile` from turbo-moonbit (`internal/moonbitlang/templates_test.go`). It reads the tools table out of `docs/{en,fr}/reference/*-tools.md` and holds every row to the file `tools.Create` actually writes, and it checks the menu's hot key by name. It is what would have caught this. Perhaps twenty minutes.
	19	3. While there: this repository's `docs/diagrams/packages.drawio` is already held to `go list` by `diagram_test.go`. turbo-go and turbo-rust still are not — that item is from the previous handoff and is still open.
	20
	21	## Watch out for
	22
	23	- The previous handoff's finding stands: turbo-go v0.4.2 and turbo-rust v0.4.2 are tagged releases whose suites fail, on stale template assertions. `01-release.tag.sh` runs `make check`, so the next tag in either will refuse to be cut.