This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: perl: cpan module's interactive mode fails
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 20 Aug 2004 18:32:11 -0400
- Subject: Re: perl: cpan module's interactive mode fails
- References: <41235C84.7060300@gtt-technologies.de> <4123B56F.6010003@gymel.com> <41245BEE.4090900@gtt-technologies.de> <921297065040.20040819105955@familiehaase.de> <41247824.2070901@gymel.com> <412481BC.3010000@gymel.com> <4124A107.2070403@gymel.com> <791319485950.20040819171336@familiehaase.de> <cg5ada$o9m$1@sea.gmane.org>
- Reply-to: cygwin at cygwin dot com
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.
cgf
--
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/