Replies: 4 comments
|
Thank you for the kind words ❤️ I traced the opacity path through OmniWM 0.5.9. Your pasted Ghostty settings should not pin the Quake opacity as OmniWM loads the Ghostty files and then applies the slider value as the final background opacity override. I also tested your exact config with OmniWM’s embedded Ghostty parser, and a later opacity override resolves correctly. Macos-titlebar-style controls Ghostty’s own windows, whereas Quake uses an OmniWM-owned borderless panel. The main difference may therefore be macOS 26.5.2 compositing as I'm on macOS 27, but I need two cold-start checks to distinguish that from live reload:
A standalone Ghostty config report cannot describe OmniWM’s embedded renderer completely, but it will expose duplicate config files, custom shaders, or other relevant settings. There are also two similar issues posted in Ghostty's own repo but none have an approved fix so far and at least one is related to your macos version. |
|
Thank you for coming back to me, @BarutSRB! 🫶🏻 This is the screenshot for step 1 (100% opacity): This is the screenshot for step 2 (10% opacity): This is the [quakeTerminal] section from ~/.config/omniwm/settings.toml: To answer 4.), yes, text/cursor remains visible. I hope any of this is helpful to you and really appreciate you taking a look here! |
|
Thanks, this identifies the problem. Your effective configuration contains: Those values differ from the ~/.config/ghostty/config you originally pasted because Ghostty loads ~/Library/Application Support/com.mitchellh.ghostty/config afterward, so that second file wins. In glass mode Ghostty intentionally renders its own background with zero alpha and expects the embedding application to provide the native macOS glass view. OmniWM 0.5.9 inherited your glass setting but did not yet provide that view. This explains why the text and cursor remain visible, while 10% and 100% opacity look identical. As a workaround for 0.5.9, change or remove this line specifically in: Then fully quit and relaunch OmniWM. Setting it only in ~/.config/ghostty/config will not override the later Application Support file. Current OmniWM head already contains the proper fix: Standard Blur overrides inherited Ghostty glass, while the Glass options provide the required native glass view. This will be included in the next release. You may also want to consolidate the two Ghostty configuration files. Rectangle is not causing this transparency problem, although it should generally be quit while OmniWM is running to avoid unrelated focus or window-management conflicts. |
|
Perfect catch, problem solved! Thank you so much for this quick resolution and your further guidance. OmniWM really made my day! |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm using OmniWM - coming from a Niri/Noctalia setup on Linux - for a few hours now and already fell in love with it. 😍 One thing I can't get sorted out:
I'm not able to adjust the "Quake Background Opacity" via its slider using the OmniWM settings pane. It doesn't have any effect, and so my Quake Terminal is always 100% transparent (and thus not usable).
Since I can't find any relevant discussions or recent issues, I suspect the problem existing on my side.
Here's my current current GhosTTY configuration (I learned that some of it is being used by OmniWM):
Any ideas on what I might be doing wrong? I'm using OmniWM 0.5.9 installed via Homebrew, MacOS 26.5.2.
All reactions