X-Spam-Check-By: sourceware.org
Message-ID: <44D0E959.70903@netacquire.com>
Date: Wed, 02 Aug 2006 11:05:13 -0700
From: Joachim Achtzehnter <joachima AT netacquire DOT com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: sed-4.1.5-2
References: <announce DOT 20060802124250 DOT GP8152 AT calimero DOT vinschen DOT de>
In-Reply-To: <announce.20060802124250.GP8152@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Hi Corinna,

You wrote:

> I've updated the version of sed to 4.1.5-2.
> 
> It reverts the default behaviour of sed back to treating CR/LF as
> lineendings, in contrast to 4.1.5-1, which only treated the trailing LF
> as lineending and the preceeding CR as the last character on the line.

Thank you very much for this fix. It will make life easier for all of us 
who struggle with a mix of native and Cygwin tools. It is very much 
appreciated that as far as line endings are concerned the attitude taken by 
Cygwin developers is not "use POSIX line endings".

At the risk of provoking another salvo of emotional responses I'd like to 
express the hope that those who take the opposite attitude with respect to 
path names ("use POSIX paths") may reconsider their position. I would 
venture to suggest that a large proportion of serious users of Cygwin must 
deal with mixed native/Cygwin tools/programs at lest to some extent. Trying 
to accommodate native standards for things like line endings and path names 
will obviously make things easier for everybody except those who use Cygwin 
as a pure POSIX environment that they never leave. Think about it this way: 
  If you say "use POSIX paths or find something other than Cygwin to do the 
job" you might as well go one step further: run a POSIX operating system. 
In other words, you're one the way to undermining the rationale for 
Cygwin's existence.

Nobody expects that toleration of native standards which conflict with 
POSIX in important ways will ever be perfect, it can't be. But this is no 
reason to tear out what's already there.

Thanks,

Joachim

-- 
work:     joachima AT netacquire DOT com   (http://www.netacquire.com)
private:  joachim AT kraut DOT ca          (http://www.kraut.ca)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/