Repository navigation
Give the Ghostty screensaver a black background - #15570
stevederico wants to merge 1 commit into
Conversation
Match the Alacritty screensaver, which already forces black, instead of falling back to the theme's terminal background. Closes omacom#14574.
[Low impact] This change appears safe to merge. SummaryAdds
No actionable issues found. Reviews (1) · Last reviewed commit: "Give the Ghostty screensaver a black bac..." · Reviewed by Greptile |
|
Tested manually on Omarchy (Hyprland, Ghostty): with this change the screensaver background is fully black, no theme color at the edges. |
|
Thanks for this. I read the diff, the launcher and the other terminals' screensaver configs, but it isn't verified or labelled yet, because classification needs two models to agree and the second (Codex Medium) didn't run: its daily review allowance was already used up. I classified it as a bug. No open pull request duplicates or competes with this one. #15243, #15359, #15614 and #15657 also touch the screensaver, but none of them changes the Ghostty config. One thing for the maintainer: Nothing is needed from you. This comes round again once a second opinion can classify it, and the worker check happens then. |
|
closing this, the ghostty screensaver file was removed in quattro (fdbe182) with the switch to the native screensaver, so this no longer applies. |
Fixes #14574
What
default/ghostty/screensaveronly set window padding, so the screensaver fell back to the theme's terminal background. This addsbackground = "#000000"(Ghostty 1.x key) so it forces black, matchingdefault/alacritty/screensaver.toml.Note: the shipped file never had the old
background-colorkey the issue mentioned (confirmed on quattro / v4.0.4). This is the intended black background as an enhancement on top of that finding.Testing
ghostty +validate-config --config-file=default/ghostty/screensaverexits 0 on Ghostty 1.3.1. A control file withbackground-colorfails withunknown fieldas expected.