Repository navigation
Conversation
Ghostty 1.3 renamed `background-blur-radius` to `background-blur` and removed the `hidden` value of `gtk-tabs-location`. The 1.3.1 binary reports both on every startup through its compatibility handler: info(cli): compatibility handler for background-blur-radius handled error, you may be using a deprecated field: error.InvalidField info(cli): compatibility handler for gtk-tabs-location handled error, you may be using a deprecated field: error.InvalidValue Both keys are replaced by their current equivalents. The effective values are unchanged (`background-blur = 20`, `window-show-tab-bar = never`), so this only removes the deprecated compatibility path before it becomes a hard break. Verified with Ghostty 1.3.1: `ghostty +validate-config` exits 0, the startup log no longer mentions the compatibility handler, and `+show-config` reports the same effective values as before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Ghostty 1.3 renamed one key and dropped one value used by
GentlemanGhostty/config. Users on 1.3+ get two deprecation notices from the compatibility handler on every startup:Deprecated compatibility keys are removed eventually, so this is a forward-compatibility cleanup rather than a cosmetic one.
What changed
background-blur-radius = 20background-blur = 20gtk-tabs-location = hiddenwindow-show-tab-bar = neverhiddenforgtk-tabs-location(it only selectstop/bottom); hiding the tab bar moved towindow-show-tab-bar(Linux/GTK).Both are documented in
ghostty +show-config --docsfor 1.3.1. No other key, comment block, or file in the repo references the old names.Evidence
Verified against the real binary,
ghostty 1.3.1-0~ppa2(the version the installer pulls for Ubuntu viamkasberg/ghostty-ubuntu):compatibility handler ... deprecated fieldghostty +validate-configghostty +show-config(effective)background-blur = 20,window-show-tab-bar = neverbackground-blur = 20,window-show-tab-bar = neverThe effective configuration is byte-for-byte identical before and after: Ghostty's compatibility handler already translated both keys, so this PR changes no runtime behavior. It only stops relying on the deprecated path.
Command used for the startup-log check (config isolated through
XDG_CONFIG_HOME, 5s timeout, GUI runs under WSLg):Compatibility note
The resulting config targets Ghostty 1.3+. Ghostty 1.2 does not know
background-blurorwindow-show-tab-bar, and this repo's installer already ships 1.3.x on both macOS (brew cask) and Debian/Ubuntu.