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 Date: Thu, 20 Oct 2005 10:42:27 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Oct 17 2005 11:54:34 Message-ID: <20051020144227.GB28514@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote: >there is a bug in this version: > >Supposed, you have a file X.sh ( exactly in this spelling ). If you >enter: > >vim x.sh ( also exactly in this spelling ) > >and write it back after any modification, the file will be renamed even >to x.sh. This behavior is very nasty if such file is used by programs >which are case-sensitive for file names, example: SCM program perforce. This isn't a vim problem. Windows filename handling is case-insensitive. I suppose that there could be a vim option to deal with this case but that would require modifying vim, i.e., PTC* by the upstream vim developers. cgf * http://cygwin.com/acronyms/#PTC -- 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/