On Monday, 4 June 2018 at 15:31:04 UTC, Steven Schveighoffer
wrote:
Windows C library has this bizarro mode for FILE * called
"text" mode, which is the default. In this mode, it scans all
output, and anywhere it sees a '\n', it replaces it with "\r\n".
Thanks, Steven.
On 6/3/18 12:24 PM, Bastiaan Veelo wrote:
On Sunday, 3 June 2018 at 15:42:48 UTC, rikki cattermole wrote:
On 04/06/2018 3:24 AM, Bastiaan Veelo wrote:
I need some help understanding where extra '\r' come from when output
is redirected to file on Windows.
First, this works correctly:
rdmd
On Sunday, 3 June 2018 at 15:42:48 UTC, rikki cattermole wrote:
On 04/06/2018 3:24 AM, Bastiaan Veelo wrote:
I need some help understanding where extra '\r' come from when
output is redirected to file on Windows.
First, this works correctly:
rdmd --eval="(\"hello\" ~
On 04/06/2018 3:24 AM, Bastiaan Veelo wrote:
I need some help understanding where extra '\r' come from when output is
redirected to file on Windows.
First, this works correctly:
rdmd --eval="(\"hello\" ~ newline).toFile(\"out.txt\");"
As expected, out.txt contains "hello\r\n".
I would
I need some help understanding where extra '\r' come from when
output is redirected to file on Windows.
First, this works correctly:
rdmd --eval="(\"hello\" ~ newline).toFile(\"out.txt\");"
As expected, out.txt contains "hello\r\n".
I would expect the following to do the same, but it doesn't:
