[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sed+windows/cygwin+newlines: improving documentation
From: |
Eli Zaretskii |
Subject: |
Re: sed+windows/cygwin+newlines: improving documentation |
Date: |
Tue, 09 Oct 2018 22:42:12 +0300 |
> Cc: Eric Blake <address@hidden>, Eli Zaretskii <address@hidden>
> From: Assaf Gordon <address@hidden>
> Date: Tue, 9 Oct 2018 13:03:15 -0600
>
> The one strange exception is:
> 1. mingw binary
> 2. reading from a file (not pipe or redirection)
> 3. using "-b"
> Then, upon *reading*, only LF (\n) are counted,
> while CR (\r) are treated like just another character (like in unix).
> But when writing, it still adds CR+LF (and converts LF-only input to
> CRLF output).
>
>
> Based on the code, I thought it would also create files
> with only "LF" when using in-place file output, but I couldn't make it
> work.
I just skimmed the recent sources, but according to what I see, it
sounds like -b only affects writing with the 'w' and 'W' commands, I
don't see where Sed switches its standard output to binary mode. Did
I miss something?
- sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/09
- Re: sed+windows/cygwin+newlines: improving documentation,
Eli Zaretskii <=
- Re: sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/09
- Re: sed+windows/cygwin+newlines: improving documentation, Eli Zaretskii, 2018/10/09
- Re: sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/12
- Re: sed+windows/cygwin+newlines: improving documentation, Eli Zaretskii, 2018/10/12
- Re: sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/18
- Re: sed+windows/cygwin+newlines: improving documentation, Eric Blake, 2018/10/18
- Re: sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/18
- Re: sed+windows/cygwin+newlines: improving documentation, Assaf Gordon, 2018/10/24