list-themes TUI QOL enhancements

[davidsanchez222]

Summary

Add Ctrl-D/Ctrl-U paging, c/C copy keys and result messages to the +list-themes save screen, and fix one key binding.

• Diff: davidsanchez222@21e4b4e
• Demo:

The change touches only src/cli/list_themes.zig. I tested it on macOS. I did not test it on Linux.

1. Ctrl-D and Ctrl-U paging

Ctrl-D and Ctrl-U move down and up 20 themes. PgDn and PgUp already do this. g and G already exist (#13376), so vim-like paging fits. It also helps users who have no PgUp or PgDn key.

2. Copy keys and result messages on the save screen

The save screen shows a line to paste in the config file, but it has no key to copy the line. Writing the theme to disk was requested in #8145, which probably will not be implemented. A comment in that discussion suggested copying the line to the clipboard, so I did that.

• c copies theme = <name>.
• C copies config-file = ?auto/theme.ghostty.
• The save screen shows the result of c, C and w next to the line it applies to. Example: theme = Atom One Light [c] copy ✓ Copied configuration line. Add visual indicator when theme saved via +list-themes #12732 requested this, and I do not see it implemented.

3. Small bug fix

In the "move down 20" binding, vaxis.Key.kp_down should be vaxis.Key.kp_page_down. A kp_down press matches both if statements and moves down 21 rows. I cannot test this because I use macOS and have no keypad.

// move down
if (key.matchesAny(&.{ 'j', '+', vaxis.Key.down, vaxis.Key.kp_down, vaxis.Key.kp_add }, .{}))
    self.down(1);
if (key.matchesAny(&.{ vaxis.Key.page_down, vaxis.Key.kp_down }, .{}))
    self.down(20);

// move up (no issue, it uses kp_page_up)
if (key.matchesAny(&.{ 'k', '-', vaxis.Key.up, vaxis.Key.kp_up, vaxis.Key.kp_subtract }, .{}))
    self.up(1);
if (key.matchesAny(&.{ vaxis.Key.page_up, vaxis.Key.kp_page_up }, .{}))
    self.up(20);

Open questions

• The save dialog is now 104 columns wide, so the longest hint line and confirmation fit. A narrower terminal clips the dialog. Is this acceptable?
• c and C have different meanings on the save screen and the list screen. The help screen explains both. Is this acceptable?

AI disclosure

I used Claude Code (Sonnet 5.5) to help write this change. I reviewed, built and tested the change myself.

[jcollie]

!vouch

[davidsanchez222]

I was already vouched from months before. Should I have made this discussion elsewhere? I have another request related to +list-fonts that I was going to make a discussion for. Should I make it here or go straight to PR?

[jcollie]

Ah, I didn't check to see if you had already been vouched. These seem reasonable and fairly small, I'd go straight to a PR.

[jcollie]

Please submit these as separate PRs. Be sure to read and understand our AI contribution policy. As far as the width of the save dialog, I'd see if you can get it to properly wrap any long logs.

[davidsanchez222]

Ok thanks. Do you mean I should do 1 and 2 as one PR and then 3 (bug fix) separate?

[jcollie]

I'd do each as a separate PR.