Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #188364 +++ eclipse-SDK-3.3RC1 on windows or linux-gtk-x86_64 Switch on Preferences : General : Compare : Ignore Whitespace, press OK Compare two text files --> Whitespace is not ignored Quit and re-start Eclipse --> Whitespace is ignored
Created attachment 68544 [details] Test project with 3 files to compare Attached ZIP contains 3 test files that should compare equal when "ignore whitespace" is switched on. Choose File > Import > Existing Projects > Archive File to import.
I think that the Preference used to be applied immediately in previous versions of Eclipse, so this may be a regression.
I have been able to reproduce this intermittently but a restart is not required to fix the problem (i.e. when I saw the problem, closing the editor and performing the compare again yielded the expected result). It appears there is a delay between when the preference is set in the dialog and when the preference is picked up by Compare with Each Other.
I've tracked this down. It is specific to the Compare With Each Other action. Here are the steps to reproduce. 1) Select two files and right-click to open the context menu but do not run the Compare With Each Other action. 2) Change the Ignore Whitespace preference 3) Execute the Compare with Each Other action In step 1) the compare configuration gets cached in the action. Running the action clears the cache. This is not a regression since this code has not been touched in 3.3. We plan on addressing Compare with Each Other issues in 3.4 since we didn't have time in 3.3.
Mass update - removing 3.4 target. This was one of the bugs marked for investigation (and potential fixing) in 3.4 but we ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
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.
