Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <3936D3A3.D4A57384@vinschen.de> Date: Thu, 01 Jun 2000 23:20:35 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Pierre DOT Humblet AT eurecom DOT fr CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: New sed in latest References: <200006012052 DOT WAA29525 AT bourgueil DOT eurecom DOT fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Pierre DOT Humblet AT eurecom DOT fr wrote: > Thanks for the effort Corinna. Although I understand the > reason isn't this pushing it too far? When working on a binary > mounted system I would expect sed to work exactly as on Unix. > Although perhaps rare, aren't there legitimate reasons to want > to keep a \r at the end of a line? Sed is often used in fairly > complicated fashions that may now be broken. 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. Corinna -- Corinna Vinschen Cygwin Developer Cygnus Solutions, a Red Hat company -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com