Community
Participate
Working Groups
I type: Thread.d<Ctrl>-Spacebar The assist gives me these top choices: currentThread Thread - Thread dumpStack void - Thread The first choice is much less relevant then the second choice. Why would I type "d" if I wanted currentThread? When working with any degree of speed, it is essential that the correct completions appear every time. Complete must be predictable, sane, and reliable. I'm using complete for speed, not because I don't know what I want. This unpredictable complete will fill my code with bugs because it ALWAYS adds the wrong thing. Since there seems to be no way to go back to a first letter only string search, I can't use context assist at all. So I will have to go back to a previous version of Eclipse. A this is a bad feature because the value of complete is lost. It should show you as little as possible and help narrow down what you want. Instead it shows as much as possible. A better solution would be to have Ctrl-Spacebar give the old first-letter-only search, and Shift-Ctrl-Spacebar give the new, whole-string search. This is very serious. You have violated your relationship with your users with this version. The same action results in entirely different software behaviour. Its as if you made Right-Click mean delete the current file, or switched the drive and brake pedals in a new car. The user upgrades and doesn't expect to have to relearn the interface - and break decade-long works habits. Unless this is fixed or a workaround is provided, I won't use Neon again. If you continue to abuse your users, I will stop using Eclipse entirely.
I can't reproduce the particular "d" problem in 4.7 head, "dumpThread" appears first. Probably fixed in 4.7, or even 4.6.3? Which Eclipse version are you using? The feature itself can be switched off via Java->Editor->Content assist->Show substring matches.
I had just tried it in 4.6.2 and it was working as expected.
I am using 4.6.3.
(In reply to Sue H from comment #3) > I am using 4.6.3. It works for me in 4.6.2 as well as 4.6.3. Something must be different on your machine. You may start by pasting the content of Help > Installation Details > Installed Software and perhaps from the Plug-ins Tab the exact versions of all org.eclipse.jdt.* plug-ins.
Created attachment 268096 [details] Installed Software Neon 4.6.3
Created attachment 268097 [details] Installed software plugin org.eclipse.jdt.*
Software versions look good. To rule out any non-standard preferences you may want to try a fresh workspace and/or installation. Do you see the same proposal order in all these experiments?
(In reply to Sue H from comment #5) > Created attachment 268096 [details] > Installed Software Neon 4.6.3
I can see Code Recommenders is installed in your IDE. Could you please uninstall it and check if you can reproduce this issue? You can also download the 4.6.3 build from here which doesn't have Code Recommenders: http://download.eclipse.org/eclipse/downloads/drops4/R-4.6.3-201703010400/ Also, based on your example in comment #0, could it be that the target of the call is a Thread? In that case, the "currentThread" proposal is more relevant than the "dumpStack" proposal.
It brings up currentThread with the "d" highlighted after I type the d. If I then press Ctl-Spacebar it switches to dumpStack. It does this in my workspace which was previously a Mars workspace. I created a new workspace with the Neon installation, and I do not see this problem. So starting with a fresh workspace created under Neon seems to be the workaround. Uninstalling Code Recommenders for Java Developers did not fix the problem.
When I hid .metadata/.plugins/org.eclipse.core.resources the problem went away. I put the original back and the problem is still gone, so hiding this file must have caused another configuration file to refresh.
Correction: Hiding /.metadata/.plugins/org.eclipse.core.runtime temporarily solved the problem.
There's not much we can do and since it works for you now, I'm closing this defect.
