ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2000/07/05/18:25:53

Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
list-help: <mailto:cygwin-apps-help AT sourceware DOT cygnus DOT com>
list-post: <mailto:cygwin-apps AT sourceware DOT cygnus DOT com>
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 5 Jul 2000 18:24:08 -0400
To: cygwin-apps AT sourceware DOT cygnus DOT com
Subject: Re: vim-5.7-2 (Bugfix-version) available for testing
Message-ID: <20000705182408.D4211@cygnus.com>
Mail-Followup-To: cygwin-apps AT sourceware DOT cygnus DOT com
References: <tba7mssm164nmvl324dt37knq51q4dot3h AT 4ax DOT com> <20000705175943 DOT B4484 AT cygnus DOT com> <eec7msgntnbbbmf1okmqp9rvg9taigghl7 AT 4ax DOT com>
Mime-Version: 1.0
User-Agent: Mutt/1.2i
In-Reply-To: <eec7msgntnbbbmf1okmqp9rvg9taigghl7@4ax.com>; from michael-ring@t-online.de on Thu, Jul 06, 2000 at 12:21:24AM +0200

On Thu, Jul 06, 2000 at 12:21:24AM +0200, Michael Ring wrote:
>On Wed, 5 Jul 2000 17:59:43 -0400, you wrote:
>>On Wed, Jul 05, 2000 at 11:42:16PM +0200, Michael Ring wrote:
>>>Corinna has thought about holding vim back until cygwin 1.1.3 is
>>>released; this would make it easier to fix problems with cr/lf because
>>>of the new mechanisms in 1.1.3
>>
>>Can you or Corinna supply specifics on what would be fixed by the
>>new mechanisms in 1.1.3?  I sort of thought that vim already was
>>textmode aware.  I was surprised to see the traffic on the mailing
>>list.
>>
>>cgf
>
>It seems to be aware of cr/lf for files that are loaded for editing.
>It does not seem to work too well with configuration files for vim
>itself having cr/lf.
>
>Easy test:
>
>create a .vimrc-file in your home
>
>open it with vim.
>
>type:
>
><ESC>:echo &fileformat
>
>response should be unix (If your home is on binary mount)
>
>now, type
>
><ESC>:set fileformat dos
>
>insert a few empy lines
>
>
><ESC>:wq
>
>now edit the file again, vim starts with error-messages:
>
>Error detected while processing /home/ring/.vimrc:
>line    2:
>Not an editor command: ^M
>line    3:
>Not an editor command: ^M
>line    4:
>Not an editor command: ^M
>Press RETURN or enter command to continue
>
>==> everything is fine until the user wants is own personal .vimrc and
>his home is on a textmount
>==> or the user wants to start some vim scripts with source and the
>scripts are either from the Windows-version of vim or also on a
>textmount.
>
>Simply using vim should not do any hard unless / is also a textmount
>but then ARGH...
>
>but fortunately every install from cygwin reverts / to a binary mount.
>
>bless god (or whoever is responsible for this) for this behaviour of
>setup.exe

Doesn't this just revert to one fopen() somewhere?  I don't see how my
recent changes help the problem.

cgf

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019