Eclipse keyboard shortcuts broken in OSX 10.5.6

Question

So I have been using Leopard for a year now, and the lastest update broke the keyboard mapping for eclipse. I use the dvorak layout, and now in eclipse if I press the ⌘ and the b key it does a build, instead of a cut(b = x).

Does anyone else have this issue, and are there any workarounds?

EDIT: The best current workaround is to upgrade to 10.5.7.

Answer 1

Eclipse 3.4.1, standard (US) qwerty layout. I haven't found any shortcut problems, I temporarily set B to do cut (by fiddling with the key assignments in the eclipse preferences), and that worked OK.

Answer 2

This is happening for me in both Eclipse and Flex Builder 3 (based on Eclipse). It's also been reported on Apple Discussions. Unfortunately I don't know any workarounds.

Answer 3

There is a witty comment to be made here about discrimination against Dvorak typists and the Dvorak layout being left out of someone's unit test--unfortunately I won't be the one to craft such a witty statement to its full potential.

I too can report this issue after upgrading from OS X 10.5.5 to 10.5.6.

Answer 4

Also broken for me. Eclipse 3.4.1. Broke as I upgraded to OSX 10.5.6. Command comma,w,s and a few others behave correctly but the majority of the keys come out as qwerty. Makes it almost impossible to use Eclipse.

Hope a fix/workaround is found soon.

Answer 5

I'm experiencing the same thing, using Eclipse 3.3.2. My workaround has been to go in to Eclipse->Preferences->General->Keys and manually re-map the assignments for the keyboard commands I use most frequently.

Answer 6

I've had the same issue, except not all the key bindings are broken. Command + S still saves, for example. But most of the commands evaluate as though I'm using QWERTY. I haven't found any solution so far except to manually remap the keys which I haven't done because its a huge pain.

Answer 7

I have the same issue. A supporting symptom: when I tried to "fix" it by using Preferences->General->Keys to remap "Undo" from F9 to Command-Z, when I typed Command-Z, it echoed as Command-/. / is the non-Dvorak key that sits in the same keyboard position as the Dvorak Z. So Eclipse is somehow getting at keys "before" the Dvorak mapping is applied by the OS.

I agree that it makes Eclipse unuseable. Help!

Answer 8

+same here with ganymede (3.4.1) and dvorak layout. It seems like they try to translate the key-codes themselves.

Can someone who changed their shortcuts (as a temporary fix) upload it somewhere please?

Answer 9

I have the same stinkin' issue too! I'm glad I'm not the only one.

Answer 10

raises hand

Another dvorak typist who can't use eclipse in 10.5.6

Answer 11

ugh! me too. Had to switch to TextMate at least for now.

Answer 12

Same here, driving me absolutely insane. Thankfully I rarely use Eclipse on OSX.

I guess I'm thankful that Cmd-S still works.

Answer 13

i have the same issue...

Answer 14

I don't generally post a "me-too", but has anyone found a solution yet for this very annoying problem?

Answer 15

I believe this is an eclipse only problem, because the same problem does not affect me when I use my Dvorak layout and other java tools such as JDeveloper or SQLDeveloper.

It drives me nuts, and I find myself actually booting windows or linux in a virtual machine so that I can use Eclipse with semi-coherent key mappings.

The odd thing is, though, that this problem did not exist to start with for me. The key mappings used to work fine in Dvorak. Then one day, poof.

I wonder if it had anything to do with the fact that non-Dvorak users on my machine change the key mapping back to qwerty.

I should mention, though I don't know if it is/isn't relevant, but I am using the CFEclipse plugin. I have not tried to invoke this behaviour with other perspectives yet.

Maybe for fun, I will try creating another local account and see if I can use eclipse to start with.

Another possibility could be the VM itself, and the way it handles the underlying keyboard interception.

Any other thoughts?

Allen

Answer 16

I'm also suffering from this problem. Any progress ?

Answer 17

Woo-hoo! It's fixed as of 10.5.7!

Answer 18

Fixed in the 10.5.7 update.