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
Message-ID: <412A5ECA.74C0B9EE@dessent.net>
Date: Mon, 23 Aug 2004 14:16:58 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: sed and dos format
References: <NGBBLLIAMFLGJEOAJCCEMEEGDNAA DOT _garbage_collector_ AT telia DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Hannu E K Nevalainen wrote:

> You wrote:
> > james pentland wrote:
> >
> >> sed has the unfortunate property that it reduces dos
> >> format line endings to unix format line endings.
> >
> > Use a text mode mount.
> 
> Using a sledgahammer for a nail?
>  Better to use unix2dos A.K.A. u2d.

I disagree.  He said he was doing this with many files.  It's far easier
to just mount the directory once as textmode and not have to change
anything than it is to edit all his scripts to run u2d afterward, and
have to remember to do that to all future scripts.  One "mount" command
versus potentially dozens of current and future script updates is hardly
a "sledgehammer for a nail".  Plus textmode mounts will keep his files
with DOS line endings no matter what processing he does, whereas "u2d"
requires that he remember to run that command any time he changes a file
with a cygwin program.  I don't see how you can advocate manually having
to do that every time when there's a feature built in to Cygwin to
handle this very thing and handle it more efficiently.

Brian

--
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/