> On 27 May 2016, at 05:07, Ben Coman <b...@openinworld.com> wrote: > > On Fri, May 27, 2016 at 2:30 AM, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> >>> On 26 May 2016, at 20:20, Peter Uhnák <i.uh...@gmail.com> wrote: >>> >>> Well I was saving e.g. STON or XML file… but some apps outside didn't >>> particularly like it… even `cat` doesn't like CR. >> >> Well, STONWriter, NeoJSONWriter and NeoCSVWriter allow you to set the line >> end convention, you are not alone in wanting the standard unix line end. > > So why don't we do it? > > CR does seem a major legacy [1] ... Early Mac OS up to version 9; > Commodore 8-bit machines, Acorn BBC, ZX Spectrum, TRS-80, Apple II > family, Oberon, MIT Lisp Machine and OS-9 > > I read [2] its a "non-issue with windows 7. Just use unix-newlines. > The only application (of the few tested) I have found which does not > understand unix-newlines as newlines is the useless notepad. For > instance it seems the following applications understand unix-newlines > just fine in windows 7: cmd scripts; powershell scripts; word 2013 (I > can open a txt file with unix-newlines, though I never use that, I can > also paste text with unix-newlines and get correct/desired line > breaking) ; OneNote 2013 (pasting text) ; wordpad (not that I use it) > ; Sublime Text 3 (naturally, just on the list because it the best; > Eclipse." > > And now Microsoft is taking small steps towards a Linux desktop ;) [3] [4] > > So it looks to me like LF wins! > It may take a while and some effort, but can we agree on a three point > strategy? > 1. Default CR line ending must change! > 2. Change it to LF. > 3. Default auto-conversion of "text" input to LF?
Yes, why not. I believe they did the same in Cuis years ago, switched the whole image, all defaults and source code from #cr to #lf and never looked back. You made a good argument, #cr on itself is obsolete, and if Windows users can live with it, there is no longer any reason not to choose for #lf. > [1] https://en.wikipedia.org/wiki/Newline#History > [2] https://blog.codinghorror.com/the-great-newline-schism/ > [3] > http://www.zdnet.com/article/microsoft-and-canonical-partner-to-bring-ubuntu-to-windows-10/ > [4] > https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspace-for-windows-developers/ > > cheers -ben > >> >>> Anyway; this is not system-breaking problem, just annoying. >>> >>> Peter >>> >>> On Thu, May 26, 2016 at 2:50 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>>> On 26 May 2016, at 14:06, Peter Uhnák <i.uh...@gmail.com> wrote: >>>> >>>> >>>> >>>> On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe <s...@stfx.eu> >>>> wrote: >>>> >>>>> On 26 May 2016, at 13:29, Peter Uhnák <i.uh...@gmail.com> wrote: >>>>> >>>>>> In general I would say that you should write either something platform >>>>>> specific or you write something specific >>>>> >>>>> Except that I cannot do that because the system doesn't support neither. >>>>> And the fact that the default line ending is CR is just bullshit… it's >>>>> 2016, not 1986. >>>> >>>> Yes, that CR is from days long gone ;-) >>>> >>>>> or #cr #lf or #crlf as needed, and/or make that last one a parameter >>>>> (OSPlatform current lineEnding). >>>> >>>> I am piping unknown content into the file, thus the need for >>>> `lineEndConvention:` and the reason of this entire thread. So as I said, >>>> the system doesn't support it. >>>> I know I can use #lf or whatnot, but I am not creating the content, I am >>>> saving it. >>>> >>>> Peter >>> >>> Well, maybe I don't understand your use case, but if you do not know what >>> is inside, why not save it as is, binary even, not doing any conversions ? >>> >>> >>> >> >> >
