Mail Archives: cygwin/2005/10/20/17:19:12
Christopher Faylor wrote:
> On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote:
>> 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 isn't a vim problem. Windows filename handling is case-insensitive.
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.
I'm guessing 6.4 has been fixed to move the old file out of the way
before writing the new file, and you thus end up with the file name in
the same case as the command line.
Anyway, the use case is illegitimate, so basically, there is no *bug* in
Vim behaving either way - it's just undocumented behavior that has changed.
Don't mix cases like this ..
(P.S. The other way that certain other editors (e.g. Emacs) deal with
this, is that they normalize the file name case when they load a file
into a buffer, by getting the "real path name" of the file - that way,
even if the rename the old file and create a new one, it'll be created
in the right case.)
--
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/
- Raw text -