rickub
turbo-editors/turbo-gopublic⑂ Fork 0
⑂ 0c719ab0fe89c178d04f38638eb87293c5706110
Branches
main
Tags
v1.0.0 v1.0.1 v1.0.2 v1.0.3 View all branches → View all tags →
Commits
⬇ Clone ▾
git clone https://git.rickub.com/turbo-editors/turbo-go.git
git clone ssh://git@rickub.com/turbo-editors/turbo-go.git

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

📦 Turbo Go 85cf23f · on 0c719ab0fe89c178d04f38638eb87293c5706110 · k33g · 16h ago
2026-09-20-load-config.md · 22 lines · 2.0 KBmarkdown
Blame HistoryOpen raw

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-go -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-go is needed), then start turbo-go 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-go already exists (configrepo.ErrExists); there is deliberately no --force.

Observed at the end of the session

demo/README.md, demo/go.mod, demo/index.html, demo/index.js, demo/main.go are deleted in the working tree (git status shows D), and an untracked demo-golang binary (6.9 MB) sits at the module root. No test or script here deletes demo/ (grep of *.sh, Makefile, *_test.go), the reflog shows no git operation, and the folder is kDrive-synced — most likely something done on the host. Not restored by this session; git checkout -- demo brings the files back if that was not intended. Note demo/go.mod is also what a root go.work must list to run go inside demo/.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22

# 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-go -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-go` is needed), then start `turbo-go` 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-go` already exists (`configrepo.ErrExists`); there is deliberately no `--force`.

## Observed at the end of the session

`demo/README.md`, `demo/go.mod`, `demo/index.html`, `demo/index.js`, `demo/main.go` are deleted in the working tree (`git status` shows `D`), and an untracked `demo-golang` binary (6.9 MB) sits at the module root. No test or script here deletes `demo/` (grep of `*.sh`, `Makefile`, `*_test.go`), the reflog shows no git operation, and the folder is kDrive-synced — most likely something done on the host. Not restored by this session; `git checkout -- demo` brings the files back if that was not intended. Note `demo/go.mod` is also what a root `go.work` must list to run `go` inside `demo/`.