| Summary: | [KeyBindings] Emacs bindings C-x C-s | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Venkatesh Prasad Ranganath <rvprasad> |
| Component: | UI | Assignee: | Douglas Pollock <douglas.pollock> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bikehead, douglas.pollock, ed.burnette, jazz-eclipse-bugzilla, kai-uwe_maetzel, spaced, stori |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 46080, 46589 | ||
| Bug Blocks: | |||
|
Description
Venkatesh Prasad Ranganath
Something seems to recognize that C-x was pressed ("Ctrl+X" shows up on the
bottom of the window, beside "Writable"), but C-x C-s just goes to the C-s binding.
i believe i've isolated the problem. after pressing ctrl+x, i put a breakpoint on the press(..) method to watch key strokes coming off of display. i press ctrl+s and it never arrives at this method. the only thing that can receive key strokes before display is accelerators on the menu (for any menu item with a single keystroke accelerator, we put the real accelerator on the menu item, not just the accelerator text). though it is redundant, as the display filter should capture everytihng, we do this trick to capture native menu behavior where possible. for instance, on the mac, if you press a key stroke corresponding to a particular menu item, the top level menu of that menu item will visibly blink). ctrl+s is being placed on the incremental find menu item as a real accelerator (for some reason it is explicitly defined as an incremental find accelerator on emacs when text editing - *kai, is this correct?*) i need to remove real accelerators off of the menu when we are in a mode. (like ctrl+x). this may be expensive, so i'm going to ask SWT if they can give me a switch here to turn off the accelerator table. Another possibiliy is dropping the accelerator table altogether. *** Bug 47301 has been marked as a duplicate of this bug. *** This works for me in 3.0. Please re-open this bug if you see this problem again.... |