RE: New sed in latest

[Peter Ring <PRI at cddk dot dk>]

The 'text' files on my WindowsNT box tend to have a '\n', and maybe also
a '\r' before that, as end-of-line character(s). For manual editing of
'text' files, we use emacs or TextPad, both of which work just fine with
Unix conventions about end-of-line.

Most of what I do with sed either assumes '\n' to be end-of-line, or
works whether or not a '\r' sits at the end of the line.

I wouldn't mind much if sed silently just dropped the '\r' at the end of
a line. But I would not like it to introduce '\r' in the output, and I
most certainly wouldn't like it to chop a file at the first ^Z.

kind regards
Peter Ring
Forlaget MAGNUS A/S
A Wolters Kluwer Company


-----Original Message-----
From: Corinna Vinschen [mailto:corinna@vinschen.de]
Sent: Thursday, June 01, 2000 11:21 PM
To: Pierre.Humblet@eurecom.fr
Cc: cygwin@sourceware.cygnus.com
Subject: Re: New sed in latest


<snip>

I don't think so. sed is a typical text tool and nearly
everyone expects sed working correct on text files and
you know what text files are under Windows.

> Also, does your change apply to piped stdin?

Yep.

> I would withdraw this comment if there was anything in the sed
> documentation to the effect that \r\n is equivalent to \n.

How shall this be? sed isn't developed for OSes with sick (IMHO)
difference between binary and text mode.

<snip>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com