2022年12月7日(水) 8:40 L A Walsh :
> [...] Similarly w/bash --
> I haven't tested it, but I'd expect bash compiled for windows
> (using mingw toolchain) to use CRLF, but LF for WSL or Cygwin.
I think there is actually no Bash compiled for Windows (i.e., the pure
Windows API on the Windows subsystem).
On 2022/12/06 10:57, Chris Elvidge wrote:
Yair, how about using the Python installed in the WSL instance.
---
Oh, I wondered why Python used CRLF, but nothing else did.
What version of python are you using? The Python for WSL,
the python for cygwin, or the python for Windows? If you
On 06/12/2022 16:00, Dale R. Worley wrote:
It seems to me that there's more going on than first meets the eye.
Yes. Yair is trying to process text files written on a Windows system
(line ending \r\n) on a Linux system (line ending \n). That Python wrote
them is neither here nor there.
Windo
It seems to me that there's more going on than first meets the eye.
My understanding is that Posix's file open function allows specifying if
the file is text or binary, and in text mode, if the underlying system
natively uses CRLF for EOL, CRLF in the file is turned into LF for the
code in a trans
Valid question.
I believe a major goal of bash will be to cross operate with other tools.
In this case, being able to read text files generated by python, when
running under WSL, seems like something bash should do.
On the question of minimal changes. I believe many bash users (some are not
hard
