Re: What should be the CRLF policy when win + Linux?
- From
- Anthony W. Youngman <wol@thewolery.demon.co.uk>
- Date
- May 18, 2010, 15:13 UTC
- Message-ID
- <U4$sctFu6q8LFwWA@thewolery.demon.co.uk>
- In-Reply-To
- <o2v40aa078e1005061625md5fede79h660a22227c4f22d1@mail.gmail.com>
In message <o2v40aa078e1005061625md5fede79h660a22227c4f22d1@mail.gmail.com>, Erik Faye-Lund <kusmabite@googlemail.com> writes
Show 5 quoted lines
>Closed source does not imply a single operating system, and you get >these issues whenever you have a project with targets systems with >different newline style. In my day job I develop closed source, >multi-platform software, using git. So it's certainly not MY most >common scenario.
And there's a lot more line endings out there than just lf or crlf.
Okay, the two I'm about to quote have, I believe, gone the way of the dinosaur, but wasn't the mac just cr? And what is *still* my favourite system, Prime (a multics derivative too), used a "packed lf", so your line ending could be either lf or lfnull depending on the line length (it was always stored on disk as an integral word-length, a word being 16 bits. So if your text was an even number of characters, the ending was lfnull to pad it to the next word boundary).
Cheers, Wol
-- Anthony W. Youngman - anthony@thewolery.demon.co.uk