Christian Schmitt wrote:
> Stefan C. M?ller wrote:
> > That's of course the safest choise for binary files. But it would
> > certainly mess up the text files.
> > While most windows tools can read LF, they all write CRLF by default,
> > some even to automatic conversion (like VC). We would end up having
> > files of both types (and files with a mix inside) in the repository. And
> > then we get trouble with all the linux tools not able to handle CRLF...
> Huh? From my experience it is more the other way around. I saw many
> Windows tool that displayed LF fext incorrectly but I have never seen a
> CRLF text in Linux being messed up. What exactly do you mean by "all the
> linux tools"?
I guess this conflict results from different comprehension of "correct
behaviour". Many (I guess: most) long-term Unix users expect an editor
_not_ to drop characters silently from a text file - which also means
displaying an "^M" if it's present,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
