mirror of
https://github.com/jesseduffield/lazygit.git
synced 2026-10-06 05:57:38 -04:00
Stefan HallerandClaude Opus 5.5
65efd3dde5
Lazygit doesn't know whether the terminal it runs in has a dark or a light background. The colors of authors, for example, have to suit one or the other, and are too pale to read on a light background. Ask the terminal. Many terminals answer CSI ? 996 n with whether they are dark or light, and send the same report again whenever that changes while mode 2031 is on. Terminals differ in what they base this on, though. kitty goes by its background color, but Ghostty goes by the dark or light mode of the operating system, even with a theme that doesn't follow it. So also ask for the background color with OSC 11. If the terminal answers that, the background decides, and a report only makes us ask for the background again. Some terminals answer OSC 11 but send no reports; ask these for the background again whenever the terminal gains focus. Turn mode 2031 off whenever lazygit hands the terminal to another program, so that the program doesn't receive the reports as typed text. For the same reason, first wait for the answers to any queries that are still outstanding, but for no longer than half a second. Locally, the answers take a few milliseconds at most, but over ssh they take a network round trip, and focusing the terminal and then pressing a key that starts an editor fits into that. Leave out the terminals that tcell doesn't send its own queries to, except for Terminal.app and WezTerm; these are only asked for the background color. This doesn't make startup any slower. tcell sends its own queries in Screen.Init and waits for the terminal to answer them. Ours go out just before, so their answers arrive before tcell stops waiting, and the color scheme is known before the first layout. tcell has no support for any of this, and drops the answers when it parses its input. Instead of adding support to tcell, wrap the tty that tcell reads from and watch the input as it goes by. For now, lazygit only writes the color scheme to the debug log. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>