Bugzilla – Full Text Bug Listing
| Summary: | [KeyBindings] New key bindings missing from Milestone 8 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Brian Enigma <enigma> |
| Component: | UI | Assignee: | Douglas Pollock <douglas.pollock> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | adalbero, arval, michaelvanmeekeren, mjohnson54, praful.kapadia |
| Version: | 3.0 | ||
| Target Milestone: | 3.0 M9 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Brian Enigma
Adding the fact that some new eclipse users like me learned to use the editor with thoses new configurations. Which is really easier to learn that the old one because of the logic of the commands. So we are lost and cannot more benefits from the new Milestone. It is unlikely that we will be providing the new key configurations. They have been pulled due to time constraints. I will investigate the F11 conflict on MacOS X. I might also add that on a Powerbook or iBook, F11 (or any of the rightmost function keys, for that matter) is an awkward two-handed operation requiring the use of the "Fn" button in the lower-left of the keyboard. As an related aside: even if the new keymappings could not be supported in 3.0-final due to time/ resource/QA issues, it would still be nice if there was a way for users to have this functionality in an "unsupported" capacity. Even if it involves replacing a file, importing a configuration, or copying files out of M7 and into M8 and beyond--unsupported keyboard mappings are better than backward, counterintuitive, or awkward ones. MVM: Could you comment on comment #3, second paragraph...? it appears that the emacs key bindings do not work inside read-only files. is this a design decision? if not, i'd be happy to file a bug. Paul: could you please file a separate bug report, and provide more details? Specifically, what functionality is not present that was there in M7 or 2.1.x. I don't see why we could not at least start by attaching a set of preferences to this bug for the other key bindings, Doug is that a problem? Mike: We could publish the new key configuration as a plug-in. I'd be willing to do it either on my own web site, or through platform-ui-home. I just don't want to step on anyone's toes by doing so. Please publish the new emacs key configuration as a plug-in. I've dumped milestone 8 and switched back to 7 because of the missing keymap! I've broken apart the F11 MacOS X conflicts as a separate bug -- Bug 57052. *** Bug 56950 has been marked as a duplicate of this bug. *** *** Bug 56497 has been marked as a duplicate of this bug. *** let's be clear, we are not talking about supporting them. I am saying we could make them available as they were in M8 and others can support/use them, doug.. on your own site is fine by me for now. Reading this report shows that this support is officially dropped, but many people, myself included truly enjoyed these new bindings much more than the old ones. My team and I are developing an application using RCP and are tracking the milestones for 3.0 as they come out, so it is important for me to be running M8, but it really hurts not having the bindings I got used to. The bug report mentions possibly publishing an unofficial plugin that would restore the new bindings, is this in the works? If there is not going to be any plugin with this support, could somone please let me know if it is possible to make such a plugin myself? I have looks at the eclopse/plugins/org.eclipse.ui_3.0.0/plugin.xml file in M7 and seen that the new bindings seem to be defined there. Is it possible to simply copy the relevant information from M7 and put it into M8?? Any info or help regarding this issue is greatly appreciated. "http://www.magma.ca/~pollockd/despumate.xhtml". Look under "Eclipse" and "Key Bindings". Follow the link, and import the plug-in. Let me know if you have any problems. Minor correction: "http://www.magma.ca/~pollockd/despumate.html" The key binding set is available on-line. There are reported difficulties with the "Command+D" prefix which I haven't had a chance to look at. Someone has also offered to host the page on SourceForge. |