This is the mail archive of the
mailing list for the Cygwin project.
RE: New sed in latest
- To: 'cygwin' <cygwin at sourceware dot cygnus dot com>
- Subject: RE: New sed in latest
- From: Peter Ring <PRI at cddk dot dk>
- Date: Fri, 2 Jun 2000 13:26:53 +0200
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.
Forlaget MAGNUS A/S
A Wolters Kluwer Company
From: Corinna Vinschen [mailto:firstname.lastname@example.org]
Sent: Thursday, June 01, 2000 11:21 PM
Subject: Re: New sed in latest
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?
> 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.
Want to unsubscribe from this list?
Send a message to email@example.com