Community
Participate
Working Groups
Build Identifier: 20100917-0705 -- Configuration Details -- Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.cpp.product) Installed Features: org.eclipse.epp.mpc 1.0.1.v20100826-2143 I'd call this a bug if it were up to me. newline style change "File" -> "Convert Line Delimiters to..." (specifically from Windows to Unix) does not actually change the text until some edit is made. If I click that, then try to "file"->"save" it does not care, does not even save, refresh has no effect. The effect can be seen clearly when "show whitespace" is on. The Consequence of this is that when I find a file in the repository which Eclipse already messed up by putting the wrong delimiters in, I cannot change it by simply selecting "File->Convert Line Delimiters" I have, in addition, to make a change, save the file, undo the change re-save the file, then commit. SPEAKING OF WHICH!!!! And why did it change my (unix originated) file to windoze style in the first place??? The file was NEVER in windows format until Eclipse decided for me --- It did NOT ask and I don't EVER work with windows format files--- I just use a windows platform. I cannot find any advice on changing the default from "Windows" as though there is no option to change that default... I have to do whatever "eclipse" decided I should be doing? Are you trying to force me to develop for windows? This is a huge distraction when it goes unnoticed and files end up in the repository in the wrong format. FYI, Differencing tools and revision control automation are not all indifferent to whitespace. This general topic comes up on http://stackoverflow.com/questions/5501521/how-to-config-eol-in-eclipse and several other online discussions without a conclusive answer. Reproducible: Always Steps to Reproduce: 0."show whitespace" on. (to see the effect... bug is not dependent on this) 1."File" -> "Convert Line Delimiters to..." -> "Unix" 2. File -> Save 3. File -> Refresh Line Delimiters remain the same!
Which editor are you using? I cannot reproduce this in the Text or Java Editor using Juno M2.
This was the editor for the C++ IDE.
(In reply to comment #2) > This was the editor for the C++ IDE. Please report the bug there.