Skip to content

v1.0.19 — Every short list opens on Ctrl+O

Choose a tag to compare

View all tags
@QuangThai QuangThai released this 11 Oct 09:39
· 21 commits to main since this release
v1.0.19
4614b08

Every short list opens on Ctrl+O

Lists that stop after their first few rows now expand like grep and diffs do, and a gh pr view body no longer offers a Ctrl+O that does nothing.

● Git status
  ⎿  9 modified · 1 untracked
     ├─ M  README.md
     ├─ M  file1.txt
     …
     └─ … 4 more files · Ctrl+O to expand

Fixed

  • A gh pr view or gh issue view body longer than eight lines offered · Ctrl+O, but expanding showed nothing more. The body now expands.
  • Every list that stops at a short head now opens on Ctrl+O: ls and find (the tools in boxed and light chrome, and through bash in every chrome), batches of reads and listings, git status, diff --stat, show --stat, log, and the commit, pull, merge, and reset cards, and gh pr and issue lists, checks, runs, and the jobs listed by gh run view (the gh run view --job log frame is unchanged). Collapsed lists look as before plus · Ctrl+O to expand on their … 4 more files row (inline bash ls/find carry it on the summary row, like the List and Find tools); expanded lists show up to tools.maxExpandedLines.

How it stays contained

  • Presentation only. One shared budget decides how many rows a list paints collapsed and expanded, and offers Ctrl+O only when expanding paints rows the collapsed list leaves out; narrow rows keep it as · Ctrl+O.
  • Nothing shown before is removed: every existing golden section is byte-identical to 1.0.18, and the new sections only add the hint and the expanded rows.

Verification

  • CI: this repository has no configured GitHub Actions workflows, check-runs, or commit-status contexts for the release commit. The local release gates below all passed.
  • npm ci and npm run check: typecheck, 398 unit/integration/golden tests (22 more than 1.0.18; seven new list fixtures run through the expand-hint property, and boxed batches get a direct test), dependency boundaries, production build, and package smoke.
  • A mutation check (the budget ignoring the expanded state) fails exactly the seven new fixtures and the batch test.
  • npm run test:e2e:readonly-tools: 25/25 packed-package CLI/RPC cases on Pi 0.99.1 with pi-hashline-edit-pro 4.5.1 (ripgrep supplied on PATH).
  • npm publish --dry-run: the expected 7-file npm artifact (148.2 kB packed).
  • Real TUI runs on Pi 1.1.0 with a deterministic local provider, an isolated agent directory, and a git repository with ten files, eight commits, and eight modified files, on the claude-code and claude presets at 110 and 40 columns: bash ls/find, the ls tool, git status, and git log show the hint collapsed, every row expanded, and one result gutter per inline block. The gh cards are covered by goldens and unit tests (the harness has no real gh output).

Tested on Windows x64 with Node 24.11.1. Linux/macOS runs were not part of this verification.

Install / update

Published on npm. The registry latest tag, gitHead (release commit), tarball shasum, a clean install whose bundle matches the release build byte for byte, and a real Pi 1.1.0 TUI run of the installed package on the claude-code preset (collapsed hint, expanded rows) have been verified.

pi install npm:@nguyenquangthai/pi-omp-theme@1.0.19
# For an existing unpinned installation:
pi update npm:@nguyenquangthai/pi-omp-theme
Assets 2
Loading