turbo-editors/turbo-go · 2026-09-02-code-navigation.md

⑂ main

2026-09-02-code-navigation.md · 27 lines · 1.6 KBmarkdown    Blame HistoryRaw
   1# Handoff — 2026-09-02 — code navigation and better editing, documentation side
5Done, on `feature/code-navigation`. Nothing is committed.
7Two tickets, both turbo-core's code: the Code menu, and ticket 19 (double-click selects a word, `Ctrl-N` inserts a line, `Ctrl-Y` deletes one, **redo moves to `Ctrl-R`**).
9All the code is turbo-core's. Turbo Go gained a new how-to (`ask-about-code.md`, EN+FR), the **Code** section in the menus reference, two keys in the keyboard reference, and an explanation section on the nine requests. Suite green, gate PASS 0/0/0.
11**This branch builds as it stands**, against the published `turbo-core v0.3.0`.
13## In flight
17## Next steps
191. Review, commit, merge.
202. After **turbo-core v0.4.0** is published: `go get codeberg.org/turbo-editors/turbo-core@v0.4.0 && go mod tidy && make check`. That is when the Code menu appears here.
22## Watch out for
24- **Redo changed key.** `Ctrl-R`, not `Ctrl-Y`. It is in the menus reference with the reason, because a key moving under someone who had learnt it is the kind of change that is only forgivable if it is said out loud.
25- **The documentation describes a menu this editor cannot show yet.** That is the same order as the last two cycles and is deliberate — but it means the docs are ahead of the binary until v0.4.0 lands.
26- **A menu item moved has to be deleted from four files, not two.** The French menus reference is separate text, not a translation applied at build time.
27- `navigate-code.md` and `ask-about-code.md` are different guides for different needs. Do not merge them: one is about moving around a file, the other about asking what a name means.

📦 Turbo Go 3d7798b k33g 10h ago	1	# Handoff — 2026-09-02 — code navigation and better editing, documentation side
	2
	3	## State
	4
	5	Done, on `feature/code-navigation`. Nothing is committed.
	6
	7	Two tickets, both turbo-core's code: the Code menu, and ticket 19 (double-click selects a word, `Ctrl-N` inserts a line, `Ctrl-Y` deletes one, redo moves to `Ctrl-R`).
	8
	9	All the code is turbo-core's. Turbo Go gained a new how-to (`ask-about-code.md`, EN+FR), the Code section in the menus reference, two keys in the keyboard reference, and an explanation section on the nine requests. Suite green, gate PASS 0/0/0.
	10
	11	This branch builds as it stands, against the published `turbo-core v0.3.0`.
	12
	13	## In flight
	14
	15	Nothing.
	16
	17	## Next steps
	18
	19	1. Review, commit, merge.
	20	2. After turbo-core v0.4.0 is published: `go get codeberg.org/turbo-editors/turbo-core@v0.4.0 && go mod tidy && make check`. That is when the Code menu appears here.
	21
	22	## Watch out for
	23
	24	- Redo changed key. `Ctrl-R`, not `Ctrl-Y`. It is in the menus reference with the reason, because a key moving under someone who had learnt it is the kind of change that is only forgivable if it is said out loud.
	25	- The documentation describes a menu this editor cannot show yet. That is the same order as the last two cycles and is deliberate — but it means the docs are ahead of the binary until v0.4.0 lands.
	26	- A menu item moved has to be deleted from four files, not two. The French menus reference is separate text, not a translation applied at build time.
	27	- `navigate-code.md` and `ask-about-code.md` are different guides for different needs. Do not merge them: one is about moving around a file, the other about asking what a name means.