Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Wed, 26 Oct 2005 11:59:40 -0400 Message-ID: <94BF3137C62D3E4CAED7E97F876585F0D03465@pauex2ku08.agere.com> From: "Williams, Gerald S \(Jerry\)" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j9QFxvc5005953 Corinna Vinschen wrote: > You're doing something differently here, perhaps in vim itself. For example, the following? :set nobackup nowritebackup If you disable both backup and writebackup, it leaves the file name unchanged when you write to it. So there's a workaround if you don't care about those features. :-) ------ Looking at the source, I think I found where VIM adjusts for pseudo-case-sensitive file names: the fname_case() function modifies the file name to match an existing file if present. The function is defined in os_win32.c and os_msdos.c but not in os_unix.c. There is also a USE_FNAME_CASE macro to protect calls to it. Simply defining that macro and function isn't enough, since it is used in the os_mswin.c version of mch_FullName(), but not it the version in os_unix.c. But it looks like a conditional call to fname_case() could be added to the end of the UNIX version, since this construct appears elsewhere in common code. You'd most likely want to use a Cygwin-specific implementation of fname_case() that doesn't convert slashes into backslashes, honors mount points, etc. gsw -- 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/