Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Resume rows no longer bold matched letters

Abierto
  • ¿Algo no está bien?
#1,349 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
76/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, documentation, testing-qa

Línea de trabajo

Start in internal/tui3/resume.go at roster.rank and roster.rows, then compare hit painting in internal/tui3/palette.go and picker.rowHit in internal/tui3/picker.go. Run the listed tmux /resume capture and inspect the existing unit and e2e coverage. Done means matching indexes render bold while selection and truncation remain intact, controls stay bold, and the manual page and change entry are updated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:chat bug sev:papercut

What happened

Cosmetic REGRESSION seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21. Lane B1, item B1-08, typed ba in /resume; the matching Bash row had no bold escape sequence. On v0.3.0 (9258f7052), the capture contained:

\e[1mBash\e[0m

/model and settings search still bold their matched letters. The regression is likely related to docs/changes/unreleased/1321-fuzzy-match-highlight.md.

Replication

Deterministic (no model).

No no-model reproduction is established; lane B1 seeded the saved conversation with a live model.

Field (real models).

Set OPENROUTER_API_KEY, seed one saved conversation under a fresh home, then capture /resume:

root="$(mktemp -d)"; export CODEAF_HOME="$root/home"; repo="$root/repo"
mkdir -p "$CODEAF_HOME" "$repo" && git -C "$repo" init -q
git -C "$repo" -c user.name=Test -c [email protected] commit --allow-empty -m base
cd "$repo" && codeaf chat --no-host --yolo --model deepseek/deepseek-v4-flash --once "say Bash"
tmux new-session -d -s resume-style -x 160 -y 44 "cd '$repo' && CODEAF_HOME='$CODEAF_HOME' codeaf chat --no-host --yolo"
tmux send-keys -t resume-style '/resume' Enter 'ba'; tmux capture-pane -ep -t resume-style

Today the matching row contains plain Bash, not \e[1mBash\e[0m.
Budget under one minute and $0.01. As controls, type the same fragment in /model and settings search and capture their bold matched letters.

Where

roster.rank and roster.rows in internal/tui3/resume.go score and render resume matches. Compare the established hit painting in paintHit in internal/tui3/palette.go and picker.rowHit in internal/tui3/picker.go. This identifies the rendering seam, not a proven cause.

The fix

Render the matched characters in each /resume result with the same bold styling used by /model and settings search, while preserving selection and truncation behavior.

Acceptance

  • e2e: Through /resume in a tmux codeaf chat, type ba, capture ANSI output, assert the matching row contains \e[1mBash\e[0m, and exit 0.
  • e2e: Through /model and settings search in the same tmux session, assert their matching Bash text remains bold after navigating and resizing.
  • Unit: Resume-row rendering receives fuzzy hit indexes and emits bold spans for exactly those indexes, including a noncontiguous-match case.
  • The manual page internal/manual/chat/home.md describes highlighted /resume matches, and the change entry's invalidates names the old belief that scoring a resume row also painted its hit.

Filed from the 2026-09-21 staging verification of 17ae56d34; the lane reports, frames and e2e logs are in the owner's handoff folder for this promotion.

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 38 min
PR fusionados (30 d)
749

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.