Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Home takes room from the current conversation tab at 19 columns

未关闭
#1,474 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
67/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

Start with internal/tui3/hometabs.go, the shared tab renderer, and the priority statement in internal/manual/chat/screen.md:192. Reproduce the 19- and 18-column cases in tmux with a conversation title beginning with T, then inspect the existing width-table and end-to-end test coverage. Done means the current tab retains a recognizable prefix, the navigation row does not wrap, boundary tests cover when home yields space, and the manual and change entry agree.

由索引模型根据 Issue 内容生成。

描述

area:chat bug sev:papercut

Seen on dev@debffabf6. Surfaced while verifying #1424; not introduced by it.

What happened

At the narrowest width still showing home (19 columns in the 2026-09-24 hand test), the current conversation's tab name shrinks to .. At 18 columns home disappears and the name reads T.... The manual promises that the current tab takes priority on very narrow frames.

Replication

Deterministic (no model). Open a conversation with a title beginning with T in codeaf chat under tmux. Resize to 19, then 18 columns and capture the tab row. Today 19 retains home and reduces the current tab to .; 18 gives the current name several cells. Repeat with a longer terminal as control.

Where

internal/manual/chat/screen.md:192 at dev@debffabf6 promises current-tab priority. The tab width allocation is in internal/tui3/hometabs.go and the shared tab renderer.

The fix

Reserve a readable minimum for the current tab before allocating home on the narrowest frames, or revise the priority statement if a one-character current tab is intended.

Acceptance

  • e2e: at 19 and 18 columns, the current tab retains a recognizable prefix, and the navigation row fits without wrapping.
  • Unit: width-table tests cover the boundary at which home yields space.
  • Align screen.md and the change entry's invalidates with the chosen rule.
主要语言
Go
星标
115
派生
14
平均合并
9 小时 38 分钟
30 天内合并 PR
730

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。