Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020121174946.023ad140@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 21 Jan 2002 17:57:31 -0500
To: neil DOT winton AT idl-bt DOT com, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: textmode broken in cygwin 1.3.6 and greater?
In-Reply-To: <F66469FCE9C5D311B8FF0000F8FE9E070FA72299@mbtlipnt03.btlabs
 .bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:35 AM 1/21/2002, neil DOT winton AT idl-bt DOT com wrote:
>Hi,
>
>I've been using Cygwin for a long time now (pre b19) but have just had
>occasion to do a fresh install on a couple of machines. I've installed with
>default textmode mounts ... but vi et al suddenly don't seem to be adding
>CRLF line endings. Redirected i/o (e.g. cat > foo.txt) is fine but ed,
>vi(m), and others just don't want to play.
>
>I've tried this with both 1.3.6 and 1.3.7-1 (haven't tried 1.3.8 yet) on
>both Win 2k and XP.
>
>I can't believe that no-one else would have found this, so maybe I've done
>something stupid -- unless this is an artefact of doing a fresh install
>rather than an upgrade. I can't test that because one of the reasons for a
>fresh install is that my machine got trashed and had to be rebuilt :-(
>
>Anyway, any insight gratefully received.
>
>         Neil

Neil,

mount modes are default indicators when a not-so-properly ported program
reads or writes a file.  Just because a directory is mounted a particular
way does not mean that a program cannot read/write a file there using some
alternate mode.  I'm sure this is the reason that you're seeing what
you're seeing.  As far as vim is concerned, you can set it to write 
either UNIX text mode (same as UNIX binary mode) or Windows text files
by setting fileformat.  See the vim help for more on this.

Very few programs (only notepad and certain constructs in files used with
VC++) have any problems reading binary files, in case you weren't aware
of this fact.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/