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/
