Community
Participate
Working Groups
We hit ctrl F very often to do searches, and it turned out that serveral of us using the GTK version were accidentally checking in code that had been reformatted. We were unaware of the key binding Esc-ctrl-F, and it turns out that there can be a long delay between when you hit esc and when you hit ctrl F. The only symptom you see is that the find dialog doesn't come up. And you'll see your code get reformatted, but this is not always obvious if your existing format is already close to the new format. 1. I'm not sure why the GTK version uses Esc ctrl F as a binding but the windows version does not. I'd suggest that the GTK version match the windows version in this respect. 2. I just realized why I've gotten in the bad habit of hitting the esc key one too many times sometimes: some things, like the autocomplete, sometimes respond too slowly to the esc key. Hit ctrl space, then esc, and in some cases this takes like a second for the pop up to go away. So i instinctively hit the esc key again, thinking it didnt take. So to sum up: As long as eclipse has speed and responsiveness problems, which quite frankly it still does very often, key sequences that begin with esc should not be enabled by default. esc is used for too many other things, and the chance of accidentally going into esc mode is too high. Thanks.
Reassigning to Douglas since he owns key bindings. Esc Ctrl-F is used because there is a GTK+ limitation where they reserve Ctrl-Shift-([A-F]|[0-9]) for typing in Unicode as hex, so a different key binding had to be selected.
Please take this up with either SWT (Bug 46580) or GTK+ ("http://bugzilla.gnome.org/show_bug.cgi?id=82011"). *** This bug has been marked as a duplicate of 42009 ***