Community
Participate
Working Groups
I have Eclipse running under Windows Vista and, in a virtual box (but this shouldn't matter), at the same time under Ubuntu. Under Windows, launch-configuration files are created and sometimes automatically updated so they have the Windows line delimiter "\r\n", and under Ubuntu, the same happens, only that the line delimiter here is "\n". This might seem a minor nuisance, but for me it is a major nuisance, because every time I fire up Eclipse under Windows, the Subclipse plug-in---correctly, from its point of view---tells me I have modified launch-configuration files, which in fact I haven't, but Eclipse has. Suggested cure: Eclipse should take the work-space-global or project-specific setting for text-file line delimiters into account when managing launch-config files in order to reduce hassle like this when launch-configuration files are checked in into an SCM and used on different platforms. This would make my days a little brighter, thank you.
So is there any update about a fix? Maybe may bug report was unnecessarily complicated: The best solution would be to use Unix line delimiters ("\n") for launch-configuration files so they are identical on all platforms. I'd be really glad to see this fixed.
*** Bug 424352 has been marked as a duplicate of this bug. ***
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. -- The automated Eclipse Genie.
Mac considers "\r" as line separator.
Far from stale. It has a duplicate and is an ongoing nuisance causing file corruptions that confuse GIT commits of changes.
Still far from stale and not yet triaged by a relecant committer. It has a duplicate and is an ongoing nuisance causing file corruptions that confuse GIT commits of changes.
