Skip to content

Conversation

rossvz
Copy link

@rossvz rossvz commented Jul 26, 2025

Even though Alacritty is the default Omarchy theme, it may be helpful to support other terminals.

This adds a ghostty-config file to each theme preset that matches which theme ghostty should use.
Most of these config themes are 1-1 with the presets, with the exception of Matte Black which uses a custom palette definition.

User would need to set up their local ghostty config to do something like

config-file = ?../omarchy/current/theme/ghostty-theme`

to conditionally apply the config from omarchy.

reloading config

at this time ghostty doesnt support programmatic reloading - so we use hyprland to iterate through any open windows and send the keyboard shortcut for reloading (CTRL SHIFT ,)

update Using the Ghostty tip, we can use pkill -SIGUSR2 ghostty to reload config

@mitchellh
Copy link

Ghostty tip (will be 1.2) supports programmatic config reloading via SIGUSR2 and systemd integrations and we’ll probably also add a dbus API before release. The signal works now for tip builds.

@dhh
Copy link
Member

dhh commented Jul 30, 2025

Happy to take this as we prepare for Ghostty being the terminal, but yes, let's target the SIGUSR2 way of triggering the config reload right away.

We could also consider having a omarchy-setup-terminal script that allows you to toggle between Alacritty and Ghostty for the moment. It's just that we need to use the ghostty-git dependency, which clocks in at about 1GB and a million dependencies, so should probably do something like "Ghostty (beta)" for the selector.

@dhh
Copy link
Member

dhh commented Jul 30, 2025

We also need to add the ghostty config to all the extra themes: https://manuals.omamix.org/2/the-omarchy-manual/90/extra-themes

@rossvz
Copy link
Author

rossvz commented Aug 1, 2025

@dhh - this is updated to use SIGUSR2 for reload. Do we want to wait for Ghostty to support this on main before merging?

re: the other themes, I can create issues in the separate theme repos indicating the expected ghostty-theme file that should be added, but we may want this landed on master first?

@rossvz rossvz force-pushed the rossvz/ghostty-themes branch from 9b270b5 to 711f9d9 Compare August 1, 2025 02:42
@RobAndrewHurst
Copy link

When do you think this is going to be a thing?

@Mohamedsayhii
Copy link
Contributor

When do you think this is going to be a thing?

September

@rossvz
Copy link
Author

rossvz commented Sep 17, 2025

@dhh with Ghostty out this could be close - I noticed that a lot of theme names have changed with 1.2 release so I can work on updating the relevant files.

Should this be part of the #1568 effort?

@dhh
Copy link
Member

dhh commented Sep 17, 2025

I tested all the theme names with Ghostty 1.2. So think they're correct on dev.

@rossvz
Copy link
Author

rossvz commented Sep 17, 2025

Got it - I think this PR isn't needed then, I didn't realize we had pulled all the theme work in that 3.0 update already

@dhh dhh closed this Sep 17, 2025
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.

5 participants