`ctrl+e` on a row of Home's standing panel does not pause the order
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Start at internal/tui3/home.go:2638 and compare the ctrl+e branch with the nearby ctrl+x branch using standsForItem(). Run make demo-home, then verify the standing-row behavior with a focused internal/tui3 key test and the stated e2e flow. Done means standing and other standing-item rows pause or resume through the same route and the row updates immediately.
Written by the indexing model from the issue text.
Description
Seen on dev@debffabf6. Surfaced while verifying #1415; not introduced by it.
What happened
ctrl+e on a standing-order row in Home's standing panel does nothing, although keys.md and home.md say it pauses the order. The key handler accepts only the homeItem row kind; ctrl+x correctly uses the broader standsForItem() check.
Replication
Deterministic (no model). Run make demo-home to seed standing orders, focus a row of the standing panel on Home, and press ctrl+e. The row remains active. Press ctrl+x on the same kind of row as a control; it reaches the standing-item action. A focused internal/tui3 key test can use the demo fixture's row without a model.
Where
internal/tui3/home.go:2638 at dev@debffabf6, in the ctrl+e branch of homeKey, switches on homeItem; the nearby ctrl+x branch uses standsForItem(). The promise is in internal/manual/chat/home.md:2285 and keys.md.
The fix
Use the standing-row predicate for pause and resume, and keep the behavior aligned with the row's visible action.
Acceptance
- e2e: in
codeaf chatwith the demo home,ctrl+eon astandingrow changes its status to paused and the row updates immediately. - Unit: Home's standing and other standing-item row kinds take the same key route.
- Correct the manual only if the chosen key contract changes; record the old dead key in
invalidates.
- Dominant language
- Go
- Stars
- 115
- Forks
- 14
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 749
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Agent-Field/CodeAF
-
area:chat feature
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Agent-Field/CodeAF#1510 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Agent-Field/CodeAF#1489 ·
Maintainers usually reply within 1 day
-
area:chat bug good first issue sev:papercut
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Agent-Field/CodeAF#1470 ·
Maintainers usually reply within 1 day
-
area:chat bug good first issue sev:papercut
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Agent-Field/CodeAF#1469 ·
Maintainers usually reply within 1 day
-
area:tests bug hygiene sev:papercut
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Agent-Field/CodeAF#1460 ·
Maintainers usually reply within 1 day
All issues in Agent-Field/CodeAF
Similar issues
-
enhancement low priority
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
eugenioenko/ttt#674 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
GoogleCloudPlatform/k8s-config-connector#13462 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vavallee/bindery#2793 · 1 comment ·
Maintainers usually reply within 1 day