Question: can't bind cmd-hjkl and cmd-e ?

[Timoyoungster]

Hello, maybe I am missing something, but I'd like to set the focus/move commands to cmd-[shift-]hjkl and it doesn't work. Those key-combinations seem to just not do anything. I also have the same problem with cmd-e. Are those combinations not supported because of macos things or can I somehow make them work?

Checklist

• [x] I've searched for duplicates. My search queries were (please don't forget to search in closed issues too):
  • cmd
  • cmd-h
• [x] I've read the guide https://nikitabobko.github.io/AeroSpace/guide
• [x] I've searched in the documentation (https://nikitabobko.github.io/AeroSpace/guide & https://nikitabobko.github.io/AeroSpace/commands). My search queries were:
  • cmd

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

[ParisTheProgrammer]

I don't think it's a question of "is it supported", you most likely will run into conflicts with other MacOS applications / system keybinds when using the cmd key. I assume this is the reason that alt/option was used by default.

I added cmd-shift-l = 'move right' to my config, and it works as expected.

Out of curiosity, can you run aerospace config --config-path and post the output? This will at least prove that aerospace is reading your config and not the default config (this happened to me once because of an error in my config).

[Timoyoungster]

The shifted ones work (mostly; I think l and h don't for me) but the non shifted ones are the main problem for me. I have disabled all macos keybinds (that I could find) in System Settings -> Keyboard -> Keyboard Shortcuts but they still don't work. And I am sure it's reading my config correctly since I've played around a bit and managed to produce a few errors in reading the config along the way and most of my other keybinds that I changed work normally.

[ParisTheProgrammer]

@Timoyoungster it is something with your setup/config as I was able to add cmd-[hjkl] to my config and after reloading it works as you would expect (tested using focus). I can use all 8 keybinds below and each of them works as intended.

If you're able/willing to post your config, might be able to troubleshoot further.

[Timoyoungster]

@ParisTheProgrammer very interesting. I have no idea what I am doing wrong. This would be my config aerospace.txt (had to upload it as txt due to github filetype restrictions)

[ParisTheProgrammer]

To test, I moved my aerospace config out of the .config directory and moved yours in its place. The only modification I made to your config before testing was the key-mapping.preset = dvorak on line 36 as I don't use that mapping.

This was quite an interesting experiment, as I would have bet money that using cmd-a to move to workspace 1 would have not worked but it works perfectly fine. I thought for sure that if an application uses cmd-a as a shortcut that it would override the aerospace shortcut but that's not what happened.

I also tested cmd-o to move to workspace 2 and cmd-u to move to workspace 4 and those worked. It's possible that the dvorak setting could be throwing a wrench in your setup?

[Timoyoungster]

I don't think so, since my initial testing was done with the setting set to querty and I only changed that to dvorak when I switched to the laptop keyboard and had to set the system keymap to dvorak. (with my external keyboard I leave the laptop on US mapping)

Really weird this whole ordeal.