-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application didn't launch error msg even though it did (Alacritty) #4
Comments
This seems to happen only with the launch_type |
My alacritty test config
|
Ha ignore the Discord issue, did not realize the test was done on which window has the focus and I am triggering the command from a terminal instead of skhd so of course discord loose the focus.. |
If i query yabai myself, it does not return Alacritty even though there is a floating alacritty window on the space which explains why Scratchpad fails to see it as well I guess.
If i start Alacritty manually and toggle it to float then yabai sees it properly:
|
Thanks for reporting the issue @tlvenn. Seems like you are using self compiled alacritty. I just tested multiple configurations. Only case that I fould when yabai fails to detect alacritty window is when launching alacritty binary compiled with This Works:
This Doesn't:
|
It appears to be Alacritty issue as suggested by yabai's creator in this thread: koekeishiya/yabai#1250 (comment) |
Ha good finding ! Ya I use Nix so it's indeed self compiled. The good news is I actually use Kitty, was merely trying to check the examples with Alacritty to make sure I was not making a mistake somewhere and I probably was given that now I can make everything works with Kitty. Super happy, awesome to have scratchpads with kitty and yazi, thanks for this project. |
Hi,
Trying to use Scratchpad and whatever I am trying it with (target title vs app), the command always spawn the floating window properly but does not manage to detect it did.
Any idea what the issue might be ?
Thanks in advance.
Env: Sonoma 14.3 / Yabai 6.0.12
The text was updated successfully, but these errors were encountered: