Problem
ghostty-switch writes selected settings to ~/.config/ghostty/overrides, which takes precedence over the base Ghostty config. The command set — profile, theme, font, current (cmd/ghostty-switch/main.go) — has no inverse. Once an override is written, the only way back to the configured default is to manually locate and delete the override file. The escape hatch from the override state lives outside the tool that created the state.
Impact
A user who applied a theme/profile/font and wants to revert to their committed config has no in-tool path. This is a gap in the tool's interface, not just a missing convenience.
Possible direction
Add a reset command (or --reset flag) that removes the override file, prints confirmation, and — if programmatic reload lands — reloads so the default takes effect immediately. Document it in --help. Handle the no-override-present case gracefully.
Problem
ghostty-switchwrites selected settings to~/.config/ghostty/overrides, which takes precedence over the base Ghostty config. The command set —profile,theme,font,current(cmd/ghostty-switch/main.go) — has no inverse. Once an override is written, the only way back to the configured default is to manually locate and delete the override file. The escape hatch from the override state lives outside the tool that created the state.Impact
A user who applied a theme/profile/font and wants to revert to their committed config has no in-tool path. This is a gap in the tool's interface, not just a missing convenience.
Possible direction
Add a
resetcommand (or--resetflag) that removes the override file, prints confirmation, and — if programmatic reload lands — reloads so the default takes effect immediately. Document it in--help. Handle the no-override-present case gracefully.