Re: [Factor-talk] EOL

IMHO, it is better to have newline always be \n. On Windows, the situation is messy because when you are dealing with Unix files you want \n but when dealing with DOS files you want \r\n. I think what we are doing now which is accepting both \n and \r\n when reading and only emitting \n when

Re: [Factor-talk] EOL

if you want to make a patch and see how it looks, sure we can talk about it! On Tue, Feb 7, 2017 at 9:53 AM, Alexander Ilin wrote: > I'm all for using \n, but being on Windows, I sometimes need to explicitly > produce native text files. In my today's use case I have coded some

Re: [Factor-talk] EOL

I'm all for using \n, but being on Windows, I sometimes need to explicitly produce native text files. In my today's use case I have coded some VS 2005 solution file transformations in Factor, after which Git showed the entire file as changed due to EOL conversion that implicitly took place in

Re: [Factor-talk] EOL

Helllo, John! Suggestion taken, thank you! Why isn't there a symbol like `eol`, so it would be possible to do something like ``` [ "\r\n" eol [ ... ] with-variable ] with-file-writer ``` Or even like ``` [ crlf [ ... ] with-eol ] with-file-writer ``` Interested in a PR? 07.02.2017,

Re: [Factor-talk] EOL

You could add the line endings yourself: "\r\n" join set-file-contents or if you are memory constrained, write them: [ [ write "\r\n" write ] each ] with-file-writer > On Feb 7, 2017, at 4:15 AM, Alexander Ilin wrote: > > Hello! > > Is there a way to use