Skip to content

Give the Ghostty screensaver a black background - #15570

Closed
stevederico wants to merge 1 commit into
omacom:quattrofrom
stevederico:fix/14574-ghostty-screensaver-bg
Closed

stevederico wants to merge 1 commit into
omacom:quattrofrom
stevederico:fix/14574-ghostty-screensaver-bg

Conversation

@stevederico

Copy link
Copy Markdown
Contributor

Fixes #14574

What

default/ghostty/screensaver only set window padding, so the screensaver fell back to the theme's terminal background. This adds background = "#000000" (Ghostty 1.x key) so it forces black, matching default/alacritty/screensaver.toml.

Note: the shipped file never had the old background-color key 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/screensaver exits 0 on Ghostty 1.3.1. A control file with background-color fails with unknown field as expected.

Match the Alacritty screensaver, which already forces black, instead of falling back to the theme's terminal background. Closes omacom#14574.
@greptile-apps

greptile-apps Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This change appears safe to merge.

Summary

Adds background = "#000000" to the Ghostty screensaver config.

  • The Ghostty screensaver uses a black background.

No actionable issues found.

Reviews (1) · Last reviewed commit: "Give the Ghostty screensaver a black bac..." · Reviewed by Greptile

@stevederico

Copy link
Copy Markdown
Contributor Author

Tested manually on Omarchy (Hyprland, Ghostty): with this change the screensaver background is fully black, no theme color at the edges.

@omarchybot

Copy link
Copy Markdown
Collaborator

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. default/alacritty/screensaver.toml and default/foot/screensaver.ini both force a black background, but default/ghostty/screensaver doesn't, so a Ghostty screensaver can show the theme's background. bin/omarchy-screensaver does set the background with OSC 11 at startup, so the next check is to launch the screensaver in Ghostty on a worker and confirm the theme colour shows on quattro but not at this head.

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: Fixes #14574 will close that issue on merge, but the background-color warning it reports comes from a file the shipped package never contained, as noted on the issue.

Nothing is needed from you. This comes round again once a second opinion can classify it, and the worker check happens then.

@stevederico

Copy link
Copy Markdown
Contributor Author

closing this, the ghostty screensaver file was removed in quattro (fdbe182) with the switch to the native screensaver, so this no longer applies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ghostty screensaver config uses removed key background-color (Ghostty 1.x)

2 participants