Hi everyone,

I wanted to share a fix for a common conflict when using Flow Launcher alongside Tiling Window Managers like GlazeWM.

The Problem

If you use the WinHotkey Plugin (to open Flow with the Windows Key) or use Alt+Space as your hotkey, Flow Launcher often fails to open when GlazeWM is running. You might also see "Current hotkey is unavailable" in the settings.

The Technical Root Cause

This conflict happens because of how Tiling WMs handle modifier keys:

1. The WM Hook: GlazeWM (and others) installs a low-level keyboard hook to manage windows. If configured to use Alt as the modifier key, it aggressively "consumes" Alt key events.
2. The WinHotkey Plugin: This plugin captures the Win key and then simulates the keystrokes of your main configured hotkey. If your main hotkey is Alt+Space, the plugin sends a synthetic Alt press.
3. The Block: GlazeWM detects this synthetic Alt press and blocks it, preventing Flow Launcher from receiving the signal.

The Solution

To bypass the WM hook, you must set Flow Launcher to use a modifier key that the WM is not blocking (usually Ctrl).

Step-by-Step Fix:

1. In Flow Launcher Settings:

   • Change the main hotkey to Ctrl+Space.
   • Why? Most Tiling WMs do not block Ctrl.

2. If you use the WinHotkey Plugin:

   • Keep the plugin enabled.
   • It will now simulate Ctrl + Space when you press the Windows key.
   • The WM will allow this signal to pass, and Flow Launcher will open instantly.

3. In your WM Config:

   • Ensure you have an exclusion rule for Flow.Launcher so it doesn't get tiled.

Confirmed working with GlazeWM v3. Hope this helps!