Layout overhaul per UX feedback — the 4-row bottom bar was too much and
mixing status info with action controls in one block felt crammed.
New chrome:
┌── row 0 ──────────────────────────────────────────────┐
│ turbo-debug dap.status msg DEBUG · STATE │ ← top bar
├───────────────────────────────────────────────────────┤
│ source code… │
│ (filename winbar now shows just %f, no DEBUG prefix) │
├── bottom tray (Console, 10 rows, full width) ─────────┤
├───────────────────────────────────────────────────────┤
│ (c)ontinue (s)tep (d)escend (r)eturn … ❓ help │ ← control bar
│ statusline (user's lualine untouched) │
│ cmdline │
└───────────────────────────────────────────────────────┘
- Top bar (2 rows, sbar_win): brand on left, dap.status() in middle,
colored state chip (DEBUG · READY/RUNNING/PAUSED) on right.
- Bottom bar (2 rows, cbar_win): controls centered, help right-anchored.
Down from 4 rows to 2 — no more crammed single-row layout.
- REPL pane removed from the bottom tray. Duplicates Console for most
workflows and the horizontal space is better spent on program output.
Users who want a REPL can hit E in debug mode to open it as a float.
- Console (bottom tray) now gets the full width and size 10 (was 8 in a
split).
- Source file winbar simplified to just " %f" — the DEBUG · STATE chip
has moved to the top bar where it belongs.
Total chrome cost: 2 (top) + 10 (tray) + 2 (bottom) + 1 (statusline) +
1 (cmdline) = 16 rows. Previous: 4 (bar) + 8 (tray) + 1 + 1 = 14.
Trade 2 extra chrome rows for vastly better layout clarity.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
swaitsandClaude Opus 4.6
869a4a36d9