-
-
Notifications
You must be signed in to change notification settings - Fork 648
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
yabai -m space --focus doesn't seem to do anything on Ventura 13.3 #1677
Comments
can you please post your |
Just fyi I am entering the 'yabai -m space' in terminal but here:
|
got it, the config and command in terminal both work fine in my machine. i have 13.2.1 OS so can't comment on 13.3. Probably delete the spaces and create them, do a reboot and test again? |
Same here, I noticed that the next and previous also seem not to work. I was able to get some output while messing around with making a new version for next
will yield this error in SKHD run in verbose I noticed the same error no matter what screen I tried to focus. However, my scripting addition is installed exactly per the instructions.
|
For the Scripting additions error install from head as mention from other issues here #1532
and that's what removes the error for me. Put like a couple seconds between commands for some reason calling them one after the other in a script doesn't work so I put |
To clarify, I am on the --HEAD branch already. I did give this a try however it didn't solve anything yet. I tried moving this window to the next one and there weren't even any errors to see:
If this is an issue unique to me, then I'll figure it out at some point in the future. I was hoping that installing the --HEAD branch would solve it but I can wait for some further progress to be mad. I'd happily supply some logs if it helps debug the situation. |
I'm having the same exact issue. I'm using the HEAD branch on Ventura 13.3 RC, just like @roni-estein. Both my hotkey to switch workspaces and the command run in the terminal do not work. Creating workspaces also doesn't work. Everything else does, however. I'm having to set the hotkey in macOS's system settings, which means I have to use a completely different hotkey than what I'm already used to. It seems the issue is with moving between and creating workspaces. |
If you searched the issues for macOS 13.3 you would find multiple comments saying that 13.3 is not supported yet. As mentioned several times before, Beta Versions will not be supported. |
and it will be fixed within 24hours after the official release is made public, as it has been done for the last 5 years. If you cannot wait for that amount of time before upgrading you are welcome to fix it on your own. |
Hi, I was just posting information in the hopes it would be helpful. I haven't used the project for 5 years and it's hard to know the ins and outs after a few hours of tinkering. Further on some of the closed comments it appeared that certain steps had resolved the issues for them. Knowing that my issue is that I'm running on an unsupported macOS is actually very helpful. It means that I haven't done something incorrectly and there is an upstream incompatibility at the moment which is great news :) no more burnt hours on this and the issue will resolve itself in time. Thanks for the reply and the effort you put into this project. |
I apologize I had thought maybe a new version had broken something unexpected and was hoping this thread would help, I clearly missed the info you mention. |
I wanted to pass on something, I have a bit of an issue leaving a problem unsolved, and I haven't looked at C since university. However, I found a brittle work around that may be interesting while waiting for an update. So it turns out you can automate key presses from the terminal. ** It will require you giving permission to the terminal to control system events. Once thats done, you can tell the system to press keys for you via the terminal! Yay! Since you have probably mapped This is probably mapped to different key-codes depending on your keyboard preference but you can look it up via this command. Assuming you have command line tools
Remember these are in hex so you need to convert them to base 10. Also note they don't just run in order. In my case Canadian macOS keybindings which as probably the same for US keybindings: # I've modified moving to the space directly as follows, I've left the original endings commented per line
# move window and focus desktop
shift + alt - 1 : yabai -m window --space 1 && osascript -e 'tell application "System Events" to key code 18 using control down' # yabai -m space --focus 1
shift + alt - 2 : yabai -m window --space 2 && osascript -e 'tell application "System Events" to key code 19 using control down' #; yabai -m space --focus 2
shift + alt - 3 : yabai -m window --space 3 && osascript -e 'tell application "System Events" to key code 20 using control down' #; yabai -m space --focus 3
shift + alt - 4 : yabai -m window --space 4 && osascript -e 'tell application "System Events" to key code 21 using control down' #; yabai -m space --focus 4
shift + alt - 5 : yabai -m window --space 5 && osascript -e 'tell application "System Events" to key code 23 using control down' #; yabai -m space --focus 5
shift + alt - 6 : yabai -m window --space 6 && osascript -e 'tell application "System Events" to key code 22 using control down' #; yabai -m space --focus 6
shift + alt - 7 : yabai -m window --space 7 && osascript -e 'tell application "System Events" to key code 27 using control down' #; yabai -m space --focus 7
shift + alt - 8 : yabai -m window --space 8 && osascript -e 'tell application "System Events" to key code 28 using control down' #; yabai -m space --focus 8
shift + alt - 9 : yabai -m window --space 9 && osascript -e 'tell application "System Events" to key code 25 using control down' #; yabai -m space --focus 9
# also like to move things to the next or previous space which I couldn't get working. My shortcuts are mapped to ctrl + right and left
# next space
# shift + alt - n : yabai -m window --display next; yabai -m display --focus next
shift + alt - n: index="$(yabai -m query --spaces --display | jq 'map(select(."has-focus" == true))[-1].index')" && \
index=$(( $index + 1 )) && \
echo "moving to space ${index}" && \
yabai -m window --space "${index}" && \
osascript -e 'tell application "System Events" to key code 124 using control down' #control + right arrow
# yabai -m space --focus "${index}" && \
# prev space
# shift + alt - n : yabai -m window --display previos; yabai -m display --focus previous
shift + alt - p: index="$(yabai -m query --spaces --display | jq 'map(select(."has-focus" == true))[-1].index')" && \
index=$(( $index - 1 )) && \
echo "moving to space ${index}" && \
yabai -m window --space "${index}" && \
osascript -e 'tell application "System Events" to key code 123 using control down' # control + left arrow
# yabai -m window --focus "${index}" && \
Ok I know it's not a fix and on occasion I've just heard the occasional ding. I'm not sure what happens if you have CAPS lock or any other modes. But if it helps someone else, thats great. I'll dust off my C at some point so I can contribute in earnest. Cheers! |
Upgrade to v5.0.3 for macOS 13.3 support. |
Damn, just upgrade to 13.3 today.
I have just install yabai, so it's v5.0.3 but still got this error.
|
I forgot to disable beta, but luckily this works even on my 13.4 installation. Perhaps try all the steps over again. I can certify it currently works on 13.3 and 13.4. You can always try my solution above for alternate commands if it doesn't work out. Good luck! |
So Yabai seems to work fine of itself but the issue is that I can't seem to switch spaces. I reinstalled the HEAD version. Re did the code sign and update the sudoers with a new sha256. Everything is tiling but `yabai -m space --focus 3' does nothing. This isn't the scripting addition error, in fact there are no errors when entering the command in terminal I believe It thinks it did it so I ran yabai in verbose tried the command again and I got the following:
here is the result of
yabai -m rule --list
if it helps:If there is anything else I can provide please let me know.
The text was updated successfully, but these errors were encountered: