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

Bug 400021

Summary: [KeyBindings] Changing the keybindings to Emacs+ unstable
Product: [Eclipse Project] Platform Reporter: Paul Webster <pwebster>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: eclipse, kermit666, mcfeber, mn, mober.at+eclipse, mthome, p.beauvoir, pelder.eclipse, pwebster
Version: 4.2   
Target Milestone: 4.3 M7   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Bug Depends on: 387728    
Bug Blocks:    

Description Paul Webster CLA 2013-02-05 15:55:07 EST
Reminder to patch back to 4.2.2+

+++ This bug was initially created as a clone of Bug #387728 +++

Steps to reproduce:
-------------------

Install Eclipse 4.2 JEE.

Add the Emacs+ software update site:

Emacs+ - http://www.mulgasoft.com/emacsplus/juno/update-site

Install the plugins:

- Emacs+
- Emacs+ options

Accept to restart.

Go to Window-Preferences-General-Keys and select the Emacs+ scheme.

Symptoms
--------
- after selecting the new scheme, it often doesn't do anything (e.g. ctrl+p and ctrl+n inside the editor don't actually move the cursor, but open a print or new.. dialog)
- one has to do the following steps to get the change of bindings accepted:

   + Change the binding scheme to default
   + Select the Restore Defaults button
   + Exit Preferences
   + Re-enter Preferences -> General -> Keys
   + Re-enable the scheme Emacs+ Scheme

- after a restart, the bindings sometimes turn back to default
- sometimes (I think when connecting to an Eclipse 3.x workspace, can't reproduce it reliably) a pop-up bubble shows up when there are duplicate keybindings (e.g. "home" and "end" keys) where the user has to choose which of these he meant (and they are usually the same in practice - such as "forward word" vs "next word").
Comment 1 Paul Elder CLA 2013-04-05 16:50:48 EDT
This now works. Tested in Kepler 4.3.0.I20130402-0800, and everything works find. Resolving as duplicate of bug 266604

*** This bug has been marked as a duplicate of bug 266604 ***