Message-Id: <200408210410.i7L4AGTR031041@delorie.com>
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
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: perl: cpan module's interactive mode fails
Date: Fri, 20 Aug 2004 23:09:35 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20040820223211.GD4833@trixie.casa.cgf.cx>
X-IsSubscribed: yes

> On Fri, Aug 20, 2004 at 09:54:55AM -0700, Shankar Unni wrote:
> >Gerrit P. Haase wrote:
> >
> >>The only real reason why textmode is needed is that notepad cannot 
> >>handle binmode (unix) textfiles.
> >
> >Unfortunately, other tools are also thrown by binmode/textmode.
> >
> >Ironically, cvs is one of them: if you have a binmode mount, 
> and run a
> >*native* cvs (e.g. cvsnt) that writes a .cvspass file with 
> CR-NL, then 
> >the Cygwin cvs tries to read it in binmode, and chokes on 
> the CR. Grrr.
> >So around here, at least, anyone who needs to use the Cygwin cvs and 
> >WinCVS on the same work area must use a textmode mount.
> >
> >So really, textmode support is unavoidable, or else all the ported 
> >tools have to be made aware of possible CR-NL line endings..
> 
> Well, nearly any native UNIX tool would be confused by CRLF 
> endings.  If you are going to use Windows and UNIX tools like 
> that then you sort of get what you deserve, IMO.  Just stick 
> with Cygwin CVS and you'll be all set.

...as long as you don't put the repository on a text mount.

-- 
Gary R. Van Sickle


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