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 sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 5 Apr 2001 13:56:25 -0400 Message-Id: <200104051756.NAA13702@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: cygwin AT cygwin DOT com In-reply-to: <20010405134001.A3662@redhat.com> (message from Christopher Faylor on Thu, 5 Apr 2001 13:40:01 -0400) Subject: Re: Proposed Changes to mount References: <000a01c0bdf3$832a1650$9531273f AT ca DOT boeing DOT com> <20010405134001 DOT A3662 AT redhat DOT com> > > Each line would have at least one trailing space followed by a CRLF line > >ending to allow the output to work correctly as either a Cygwin shell script > >or a Win32 batch file. > > I don't understand the need for a space. There should be no reason for that. It was my suggestion, and needs a second patch to work right. The reasoning is that mount can always create the file in text mode (CR/LF), so that it can always be used as a .bat file. However, it can also be used as a shell script *if* the extra CR (which would otherwise be appended to the last argument) is isolated *and* if mount checks the last argument to see if it's a CR and strips it. Alternately, mount could just check the last arg to see if it has a CR appended, and strip it. Perhaps it should do both. The idea is to make mount bulletproof wrt text conversions in scripts, and allow one mount option to be used for creating both batch files and shell scripts. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple