Maria José Solano

@nonetrix in fact, the issue is only reproducible with the git Hyprland image, but it's fine with the latest release (at least this is what I am experiencing).

@sjcobb2022 thank you for the careful investigation! > This is definitely a hyprland-caused issue Does this mean that this is a Hyprland _bug_, or that these intentional changes broke Wezterm...

@sjcobb2022 Makes sense! And yes, I also see GTK-based apps (like Thunderbird or my ags widgets) working just fine.

> the latest release(20240203-110809-5046fc22) works fine. Do you have the same setup I described? I just updated `hyprland-git` and `wezterm-nightly` on Fedora Asahi and I'm still experiencing this issue.

> is there a work around for this? @MariaSolOs @sjcobb2022 Setting `config.enable_wayland = false` also works, but I'm not sure of the impact of this.

Is the list above for open issues only? Asking because I would love to see #2993 in the next release :)

Okay I debugged this a bit and removing [this line](https://github.com/folke/which-key.nvim/blob/38b990f6eabf62014018b4aae70a97d7a6c2eb88/lua/which-key/keys.lua#L107) fixes it. For some reason in [this call](https://github.com/folke/which-key.nvim/blob/38b990f6eabf62014018b4aae70a97d7a6c2eb88/lua/which-key/keys.lua#L116) the group has a name but `children` is empty, while [here](https://github.com/folke/which-key.nvim/blob/38b990f6eabf62014018b4aae70a97d7a6c2eb88/lua/which-key/keys.lua#L117) there...

@ColinKennedy the docs indicate that you should disable operators **before calling setup** (refer to the comment in the example of [this section](https://github.com/folke/which-key.nvim#-operators-motions-and-text-objects)).

@ColinKennedy I think you've misunderstood what the setting does. `presets.operators` will just disable the built-in Vim operators (and so as your picture clearly shows, `which-key` isn't showing things like `dd`,...

@ColinKennedy glad I could help :)