Community
Participate
Working Groups
I have 4.7.3a, not 4.7.3, but that wasn't an option in the dropdown. Quite often, I've gone into Preferences and "Keys" and entered a string in the filter field to see only the functions containing that string. Today, I discovered that this now does nothing. I was looking for the list of functions with "zoom" in the name. I entered "zoom" in the filter field, but the list of bindings didn't change. I then erased "zoom" and tried junk strings, and nothing made any difference.
I tried with http://download.eclipse.org/eclipse/downloads/drops4/R-4.7.3a-201803300640/ and also our 4.8 RC1 candidate http://download.eclipse.org/eclipse/downloads/drops4/I20180516-2000/. The filtering works fine with both of them. Is there anything in the .log? Did you maybe install something that breaks it?
No, there's nothing related in the log. I see the same behavior in the main filter field in the preferences dialog. Entering a value does nothing.
(In reply to David M. Karr from comment #2) > No, there's nothing related in the log. > > I see the same behavior in the main filter field in the preferences dialog. > Entering a value does nothing. Did you test with a build from comment 1 and a new workspace?
(In reply to Dani Megert from comment #3) > (In reply to David M. Karr from comment #2) > > No, there's nothing related in the log. > > > > I see the same behavior in the main filter field in the preferences dialog. > > Entering a value does nothing. > > Did you test with a build from comment 1 and a new workspace? I have not done that yet. I'll proceed with that, but it will take some time.
Hmph. I appeared to have fixed it. I find it hard to believe the change I made is the "root cause". It's more likely to have tweaked some sort of race condition in the other direction. I noticed that my Windows installation that was seeing this symptom was running JDK 1.8.0_152, and the Linux VM was running 9.0.4. I installed 9.0.4 on Windows and changed it to use that. No more symptom.
(In reply to David M. Karr from comment #5) > Hmph. I appeared to have fixed it. I find it hard to believe the change I > made is the "root cause". It's more likely to have tweaked some sort of > race condition in the other direction. > > I noticed that my Windows installation that was seeing this symptom was > running JDK 1.8.0_152, and the Linux VM was running 9.0.4. I installed > 9.0.4 on Windows and changed it to use that. No more symptom. Thanks for the update.
