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 VS 2005
> solution
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 `chan
maybe, there are some historical differences that make newlines funny
business
https://blog.codinghorror.com/the-great-newline-schism/
I'd love to just use '\n' everywhere.
On Tue, Feb 7, 2017 at 9:24 AM, Alexander Ilin wrote:
> Helllo, John!
>
> Suggestion taken, thank you!
>
> Why isn't the
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, 16:40,
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 `change-file-lines`, but
Hello!
Is there a way to use `change-file-lines`, but override EOL to be CR+LF in
the output?
If not, what's the alternative solution?
---=---
Александр
--
Check out the vibrant tech community on one of the wo
