Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm building a DefaultKeyBinding.dict with some useful functions.

One of the functions I'd like is uppercaseWord:, but when I try to bind this to Option+U, OS X ignores this binding. It also ignores the other "composing" bindings, Option+I,E etc.

Is there anyway I can make OS X respect my bindings? I know it ignores some of them to ensure applications run properly, but I haven't seen a list of them anywhere. Does it exist?

EDIT: It seems dead keys take precedence over bindings. The solution is to remap the dead keys elsewhere so my normal keys will work.

share|improve this question
Have you logged out and back in to load the DefaultKeyBinding.dict? Do any combinations with Option+Character work? Are these broken combinations assigned a character with your current keyboard layout (e.g. Option-S = ß with British layout); what if you use that character instead? – Daniel Beck Jun 3 '11 at 7:19
up vote 2 down vote accepted

The only option I can think of would be to use Ukelele to create a custom keyboard layout without the dead key states under option.

Apart from dead keys, there aren't that many key combinations that couldn't be overridden. The only ones I've found are shift-command-arrows, control-option-command-arrows, and command-tab.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .