Xcode 14 Key Bindings: Default Conflicts and Non-Functional Bindings

Without any customization whatsoever, there are 25 key binding conflicts in Xcode 14. This is the default set that Apple created. What's more, many of the existing key bindings do not work.

One important binding that I use with muscle memory is "insert new line and leave section before it." Xcode uses control+O for the default binding, but it doesn't work. Furthermore, I can't add a custom binding for it. Xcode notes a conflict for ⌘+return. Every other editor uses this binding by default, so I can't understand why Xcode won't allow it, even as a customization.

Does anyone know how to resolve these conflicts, fix the bindings, and/or force Xcode to respect custom bindings?

Thanks in advance.

Answered by markwyner in 758075022

It's been a couple of weeks and there hasn't been a reply to this. Does anyone from Apple view these posts? I've seen posts from other people elsewhere on the web related to this issue. It's known, at least by those of us using Xcode. I'd love to know if anyone has a fix for this. Thanks in advance.

Accepted Answer

It's been a couple of weeks and there hasn't been a reply to this. Does anyone from Apple view these posts? I've seen posts from other people elsewhere on the web related to this issue. It's known, at least by those of us using Xcode. I'd love to know if anyone has a fix for this. Thanks in advance.

It's June 28th, 2024 and I have 23 conflicts in key bindings. I get very strange behavior when using the escape key - which should do one thing - escape (pop) out.

Xcode 14 Key Bindings: Default Conflicts and Non-Functional Bindings
 
 
Q