turbo-editors/turbo-pythonpublic Fork 0
v1.0.0
Commits
Clone
git clone https://git.rickub.com/turbo-editors/turbo-python.git
git clone ssh://git@rickub.com/turbo-editors/turbo-python.git

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

📦 Turbo Python 6fc62ea · on v1.0.0 · k33g · 11h ago
2026-09-09-alt-t-fix.md · 23 lines · 1.7 KBmarkdown
Blame HistoryOpen raw

Handoff — 2026-09-09 — a wrong hot key, found by the next editor

State

Ten documentation files changed, both languages, uncommitted. Nothing else in this repository was touched and its suite was not re-run.

What was wrong

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.

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.

explanation/architecture.md also said "all three editors" in both languages. It is four now.

Next steps

  1. Commit.
  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.
  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.

Watch out for

  • 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.
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# Handoff — 2026-09-09 — a wrong hot key, found by the next editor

## State

Ten documentation files changed, both languages, uncommitted. Nothing else in this repository was touched and its suite was not re-run.

## What was wrong

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`.

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.

`explanation/architecture.md` also said "all three editors" in both languages. It is four now.

## Next steps

1. Commit.
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.
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.

## Watch out for

- 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.