1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
# Handoff — 2026-09-20 — `-load-config` (needs turbo-core v1.0.3)
## State
- `-load-config <url>` wired in `main.go`, three tests in `main_test.go`, docs EN+FR updated. Green under the umbrella `go.work` (`turbo-editors/`), which resolves turbo-core to the local checkout.
- **`go.mod` still says turbo-core v1.0.2** — `GOWORK=off make check` fails until turbo-core v1.0.3 is tagged and this is re-pinned. Even under the workspace, the two release-script tests (`TestTheTagScript…`) fail for the same reason: they build a copy of the module outside it. Everything else is green.
## Next steps
1. When turbo-core v1.0.3 is tagged: `go get rickub.com/turbo-editors/turbo-core@v1.0.3 && go mod tidy && GOWORK=off make check`.
2. Try it for real: in an empty directory, `turbo-moonbit -load-config https://rickub.com/turbo-editors/configs/tree/main/golang-init` (the sample repository holds `.turbo-go` only — for this editor a directory with a `.turbo-moonbit` is needed), then start `turbo-moonbit` and check the settings took.
3. Then `./01-release.tag.sh` as usual.
## Traps
- The sample configs repository is `rickub.com/turbo-editors/configs`; its git address is `git.rickub.com`, which `configrepo` tries second. A wrong first candidate costs one `ls-remote`, not the load.
- The editor refuses when `.turbo-moonbit` already exists (`configrepo.ErrExists`); there is deliberately no `--force`.
|
