Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 122266

Summary: [key binding] Provide key bindings for text editing commands
Product: [Eclipse Project] Platform Reporter: Randy Hudson <hudsonr>
Component: TextAssignee: Platform-Text-Inbox <platform-text-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 Keywords: helpwanted
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Randy Hudson CLA 2005-12-28 15:42:26 EST 
I'm trying to inherit keybinding assignments from the default text scope. These commands are defined, but they are not mapped to the ARROW keys. This is strange, since the arrow keys do in fact invoke these actions in the default text editor.

I am writing a custom widget and would like to use actions/handlers for all "actions". It seems like the text editor is relying on the widgets default handling of these keystrokes.
Comment 1 Dani Megert CLA 2006-01-03 06:56:57 EST 
So far we explicitly (design decision) do not provide the key bindings for (most) standard 'Text Editing' commands but provide (and handle) the commands to allow adding of additional key bindings. In the past this made it more flexible for different platforms (e.g. Command vs. Ctrl).

On our side there are currently no plans to add this but we'd accept a patch that provides the key bindings for the complete set of standard text editing commands.
Comment 2 Lars Vogel CLA 2019-09-04 02:58:56 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--