This problem seems to be extremely rare, but it has been reported that the F3 key binding for the Java editor seems to disappear in some configurations. A workaround may be to reconfigure the keybinding if it no longer seems to work (Eclipse preferences > Keys > assign “Open Declaration” to F3).

Blocks Spoofax/209.

Submitted by Lennart Kats on 6 July 2010 at 17:29

Karl said he knew how to reproduce this issue.

I’ve now seen this (for the first time) after installing TeXlipse. TeXlipse also adds a new F3 key binding for “in latex editor”, so having a third party plugin may be what triggers it. Other than that, it seems my Eclipse installation has two more key bindings for F3:

• Open definition for “editing text”

• Open declaration for “in windows”

Once the first one is unbound, the other one is also unbound. Then the problem can be solved for the Java editor by binding “open declaration”, or for the IMP editor by binding “open definition”. I’m not sure if they can both work if TeXlipse or some other third party plugin is installed.

At the Spoofax level this problem might be fixed by binding org.strategoxt.imp.runtime.resolveReferenceCommand only to F3 in the context “in IMP editor”, if we can create such a thing. Alternatively it might be possible to add a new event handler class for the standard “open declaration” binding?

I think I’ve seen it again. But maybe it’s not a keybinding problem at all? Control/command-clicking also didn’t work. Control/command-T did.