Openning file always fails if mis-typed (with wrong case) first time

[GoogleCodeExporter]

I'm not exactly sure if the summary is the best description of this
problem, but it's the closest I think of at the moment.

Suppose a file exists called "A.txt". I try to open it with a lowercase name:

:e a.txt

MacVim thinks this is a new file, because this file does not exist. I kill
this buffer:

:bd

Then, I try to re-open the file with the correct case:

:e A.txt

MacVim thinks I'm still trying to open "a.txt", so it opens a new buffer
with "a.txt" as the heading. The only way I can open "A.txt" is if I close
out this window (all buffers)...

:qa

... and open a new window or run "mvim A.txt" from the command line. Note
that the same issue appears when I run "mvim a.txt" from the command line.

Also note that tab completion in MacVim's command mode still identifies the
correct file name ("A.txt" instead of "a.txt").

I'm using MacVim 0801A on Mac OS X 10.5.1 b9B18 on a 1.5GHz PowerBook G4. I
recently reformatted my drive with case-sensitive HFS+ and installed
Leopard. My theory is that this problem won't occur with case-insensitive
HFS+, but I don't have a computer to prove it.

Original issue reported on code.google.com by sean.lea...@gmail.com on 7 Feb 2008 at 11:10

[GoogleCodeExporter]

The same thing happens on case-insensitive HFS+ (I just checked).  It has 
something to do with how Vim is 
compiled I am guessing...I have noticed on some systems that tab-completion in 
Vim is case-sensitive but it is 
case-insensitive on the Mac (and this issue is somehow related).  You should 
ask about this on the vim_dev (or 
vim_mac) mailing list; there you should be able to get a better answer.

/Björn

Original comment by bjorn.winckler@gmail.com on 7 Feb 2008 at 1:13