Summary: | [key binding] Find Next is mapped to Command+K instead of the normal Command+G | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Alex Blewitt <alex.blewitt> |
Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | andre_weinand, douglas.pollock, markus.kell.r |
Version: | 3.3 | ||
Target Milestone: | --- | ||
Hardware: | Macintosh | ||
OS: | Mac OS X - Carbon (unsup.) | ||
Whiteboard: |
Description
Alex Blewitt
2004-03-30 15:59:28 EST
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. |