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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: Re: VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Oct 17 2005 11:54:34
Date: Fri, 21 Oct 2005 12:04:49 -0400
Message-ID: <94BF3137C62D3E4CAED7E97F876585F0D033F0@pauex2ku08.agere.com>
From: "Williams, Gerald S \(Jerry\)" <gsw AT agere DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j9LGB30f021810

Shankar Unni wrote:
> But I think it's worth mentioning that 6.3 doesn't do this (change the
> case of the name when writing back). It overwrites the old file when
> writing back, thus preserving its case.

More to the point, the windows version of vim 6.4 doesn't do
this, either. So there is some code in there somewhere that
knows about case-wacky-pseudo-sensitive file systems (OK, it
probably just has #ifdef WIN32 around the old method, but
still...).

gsw

P.S. It might be possible to come up with a workaround using
     some trickery within VIM (e.g., do an ls on the dirname
     of % via event hook when you open a new file and either
     rename % somehow or hook into the file write event).


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