Trick for handling newlines:
If the file in the repository has different nl chars from the one your
comparing with in your workspace, you can easily just switch the
workspace one to match: highlight the file, and use the file menu ->
convert line delimeters to... and switch them to match.
I think Thilo's point was that using Eclipse compare, you *can* see
which lines, even which parts of lines changed. Not sure if the Eclipse
SVN plugin lets you compare 2 revisions, though...
-Marshall
Thilo Goetz wrote:
Adam Lally wrote:
On 11/15/06, Thilo Goetz <[EMAIL PROTECTED]> wrote:
Yes, that file had tabs which made it unreadable. On the other
hand, if
you use Eclipse, it is not at all hard to see what changed as the
structural compare will show you only logical differences.
For me, the Eclipse Java Structure Compare on SofaTest.java just tells
me that testMain() and testSofaDataStream() have changed, it doesn't
tell me what in those methods has changed.
Not sure I follow you. I admit that the "ignore whitespace" option is
less than perfect (it can't seem to handle newlines correctly, which
is a pain).
--Thilo
