Community
Participate
Working Groups
The Find Next is currently mapped to Command+K (with Find Previous being mapped to Command+Shift+K). However, Mac apps use Command+G to find the next element, and Command+Shift+G for previous element (see TextApp for an example). I think there is a good argument for making the Mac commands for finding the same as normal apps, because otherwise it's going to confuse people using it. Command+G is currently bound to 'Declaration in workspace' which is probably much less important than a find next/previous.
I concur. This was part of the massive overhaul of key bindings that is being deferred from 3.0. Perhaps this particular piece could be considered on its own for 3.0. JDT: can you comment on this?
This is still mapped as Command+K on the Mac.
We could change that but the question is whether long time Eclipse users would accept Command+G no longer searching for declarations and Command+K no longer finding the next match (we would need to map Command+K to search for declarations). André, what's your take on this one?
Isn't the 'find next' a global thing, as opposed to the 'find declarations' a JDT thing? Wouldn't those RCP/other text users be expecting a more normal Eclipse mapping?
Firefox, Thunderbird, and Acrobat Reader also use Ctrl+G / Ctrl+Shift+G for Find Next / Find Previous on Windows. I'd say this is the new trend.