Maria José Solano

Of course. Here's the log file from Wezterm: [wezterm.log](https://github.com/hyprwm/Hyprland/files/14388585/wezterm.log)

I know, it's quite strange... It's not happening with the stable image, which gives me the following `hyprctl systeminfo` output: Hyprland, built from branch HEAD at commit 84ab8d11e8951a6551d1e1bf87796a8589da6d47 (props: bump...

I will be adding the kitty logs in a bit, currently AFK. For my own knowledge, why do you say it's wezterm's fault? @vaxerski

I see. I had never had issues with Wezterm until now :( As promised, here are the kitty logs: [kitty.log](https://github.com/hyprwm/Hyprland/files/14391133/kitty.log)

> no errors here in the log But `kitty` is still not opening.

@vaxerski Even with an empty `kitty.conf` I have this behaviour... It seems like this isn't Hyprland's fault, and the last thing I want is to make you more busy than...

I haven't tried foot yet (I'm not that desperate since I still have a working setup lol) but I'll try that. I will continue investigating. In the meantime, I think...

@vaxerski yeah we can close this and let https://github.com/wez/wezterm/issues/5067 track the problem with wezterm.

> **Questions**: > > 1. @MariaSolOs Should "inline" be replaced with "inlay" in _all three_ of these? That's the goal. > 2. @MariaSolOs Is this the relevant documentation for inlays?...

It seems like this is also causing issues with pickers like `fzf-lua`. See this issue for example: https://github.com/ibhagwan/fzf-lua/issues/1294