Re: sed 4.1.5 adds extra CR with input file path in Windows format

2006-06-27 Thread David Mastronarde
On Tue, 27 Jun 2006, Dave Kilroy wrote: On 6/27/06, David Mastronarde wrote: On Sun, 25 Jun 2006, Dave wrote: > David Mastronarde wrote: >> After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were >> being converted from CRLF to CRCRLF when the input file was specified >> with

Re: sed 4.1.5 adds extra CR with input file path in Windows format

2006-06-27 Thread Dave Kilroy
On 6/27/06, David Mastronarde wrote: On Sun, 25 Jun 2006, Dave wrote: > David Mastronarde wrote: >> After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were >> being converted from CRLF to CRCRLF when the input file was specified >> with a windows file path: >> >> % sed -e 's/g5a/s

Re: sed 4.1.5 adds extra CR with input file path in Windows format

2006-06-27 Thread David Mastronarde
On Sun, 25 Jun 2006, Dave wrote: David Mastronarde wrote: After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were being converted from CRLF to CRCRLF when the input file was specified with a windows file path: % sed -e 's/g5a/setname/g' < 'c:\cygwin\home\mast/sedtestin' > ! s

Re: sed 4.1.5 adds extra CR with input file path in Windows format

2006-06-25 Thread Dave
David Mastronarde wrote: After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were being converted from CRLF to CRCRLF when the input file was specified with a windows file path: % sed -e 's/g5a/setname/g' < 'c:\cygwin\home\mast/sedtestin' > ! sedtestout Converting the path to cyg

sed 4.1.5 adds extra CR with input file path in Windows format

2006-06-24 Thread David Mastronarde
After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were being converted from CRLF to CRCRLF when the input file was specified with a windows file path: % cat sedtestin $ccderaser -StandardInput InputFile g5a.st % od -c sedtestin 000 $ c c d e r a s e