Bug 239688 - [KeyBindings] Imported JDT-CDT keys bound to "Undefined Command" bindings that can't be removed
Summary: [KeyBindings] Imported JDT-CDT keys bound to "Undefined Command" bindings tha...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 239625
Blocks:
  Show dependency tree
 
Reported: 2008-07-05 13:37 EDT by alan ezust CLA
Modified: 2019-09-06 16:13 EDT (History)
2 users (show)

See Also:


Attachments
keys33.epf (19.32 KB, application/octet-stream)
2008-07-05 13:37 EDT, alan ezust CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description alan ezust CLA 2008-07-05 13:37:34 EDT
Created attachment 106642 [details]
keys33.epf

Build ID: Build id: I20080617-2000

Steps To Reproduce:
1. Try importing the attached eclipse keys preferences, created from JDT but I'm importing into CDT.
2. Try to bind F1 or Ctrl+Shift+R to any other action.
3. Notice an "Undefined Command" which is associated with that key. 
4. Try to remove the Undefined Command. You can't.

Note: this keys preferences was imported from JDT, and those bindings were quite language-specific, so I guess they don't exist in the CDT. 

But if even if it's undefined, it should still let me remove and rebind it.



More information:
Comment 1 Patrick Schonbach CLA 2008-07-08 10:20:40 EDT
Wouldn't it be helpful to have a function that cleans up all undefined commands? Removing them one by one is quite tedious.
Comment 2 alan ezust CLA 2008-07-08 16:08:07 EDT
yes, that would be better. Either that, or just make sure that when one re-binds the key to something else, those undefined actions get cleared automatically.
Comment 3 Paul Webster CLA 2009-03-02 11:41:48 EST
Updated as per http://wiki.eclipse.org/Platform_UI/Bug_Triage
PW
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:12 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. 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.