This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bug? Mixed CR/LF and LF line endings from different programs

On Fri, Aug 30, 2002 at 05:43:24PM +1000, wrote:
>On 29 Aug, Christopher Faylor wrote:
>>  On Fri, Aug 30, 2002 at 10:19:38AM +1000, wrote:
>>  >On 29 Aug, Christopher Faylor wrote:
>>  >>  On Thu, Aug 29, 2002 at 09:21:10AM -0700, Shankar Unni wrote:
>>  >>  >Christopher Faylor wrote:
>>  >>  >>awk and sed open their standard input in textmode.  This is by design.
>>  >>  >
>>  >>  >Don't they open their stdout in textmode, then?  Otherwise they should
>>  >>  >have been "fixed up back" to \r\n when they wrote the lines out, no?
>>  >>  
>>  >>  I think you can draw your own conclusions on what is happening pretty
>>  >>  easily.
>>  >
>>  >Yep.  I don't understand why, though.
>>  awk and sed both do input text and, on output, default to the mode
>>  derived from the mount table.  So, \r\n is changed to \n internally and
>>  is changed to whatever is appropriate on output.  That means that a '$'
>>  will match eol in sed but may still output a \r\n.
>Good.  Below, you say that a binmode  mount will force all \n outputs,
>which is the opposite of what I want.  I'm using a textmode mount, and
>still getting \n output for awk and sed, which seems be doing the
>opposite of what would be appropriate.

Your tools are:  mount and CYGWIN=[no]binmode.  You can play with those
to see what's available.  There are only a limited number of options so
it shouldn't be too hard to figure out what's going on.

>Maybe I can just ask this: what combination of mount mode and CYGWIN
>setting will ensure that all text processing will generate
>platform-native (CR-LF) output?

There is no such setting.  If I had a time machine, I'd go back and make
sure that this CRLF crap was never introduced.

>>  >matching - depending on the mount type - DOS or Unix, seems correct to
>>  >me.  Yet awk and sed don't do it.  This suggests that they're not
>>  >opening the output file in text mode,
>>  They're not opening the output file in any mode.  The mount type of the
>>  disk prevails.  Forcing them to write \r\n line endings is exactly the
>>  wrong thing to do.  The default for cygwin should be binary out.
>>  Actually they probably should both be using "automode" (input text,
>>  output binary) but both packages probably predate that.
>Does that mean there *is* a problem?


>>  >>  I just wanted to make sure that people understand that the behavior is
>>  >>  not a random event.  It comes up from time to time here and I thought
>>  >>  that it bears repeating that both are working the way they are designed
>>  >>  to work.
>>  >
>>  >I understand that it's not random, but now I'm at a loss to understand
>>  >why that behaviour was chosen.
>>  >
>>  >So, what's the recommended way for using Cygwin for any sort of text
>>  >processing?
>>  Mount everything in binmode if you want to only see \n line endings.
>That's the opposite of what I want.  I want consistent, CR/LF line
>endings.  Surely that's possible?


>>  Actually, if it does that's a bug.  nobinmode only works on things for
>>  which no mount info can be derived, like pipes.
>Perhaps the CYGWIN binmode option could do with some extra explanation
>in the user guide.  I confess I had to experiment to get the desired

Nah.  The explanation is just fine.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]