[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handling files with CRLF line ending
|
From: |
Chris Elvidge |
|
Subject: |
Re: Handling files with CRLF line ending |
|
Date: |
Tue, 6 Dec 2022 18:57:10 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Lightning/5.4 |
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.
Windows text files have to be converted to Linux format before
processing - either inline (tr -d '\r') or in mass (dos2unix).
Expecting bash to cope is a non-starter.
Yair, how about using the Python installed in the WSL instance.
--
Chris Elvidge
England
- Handling files with CRLF line ending, Yair Lenga, 2022/12/03
- Re: Handling files with CRLF line ending, Greg Wooledge, 2022/12/03
- Re: Handling files with CRLF line ending, Yair Lenga, 2022/12/03
- Re: Handling files with CRLF line ending, Chet Ramey, 2022/12/05
- Re: Handling files with CRLF line ending, Yair Lenga, 2022/12/06
- Re: Handling files with CRLF line ending, Dale R. Worley, 2022/12/06
- Re: Handling files with CRLF line ending,
Chris Elvidge <=
- Re: Handling files with CRLF line ending, L A Walsh, 2022/12/06
- Re: Handling files with CRLF line ending, Koichi Murase, 2022/12/06
- Re: Handling files with CRLF line ending, Chris Elvidge, 2022/12/07
- Re: Handling files with CRLF line ending, Ángel, 2022/12/08
- Re: Handling files with CRLF line ending, Chris Elvidge, 2022/12/08