I opened a file (foo.f90) with macvim that had the .f90 suffix. Then,
I realized I wanted it preprocessed. [No jokes about fortran ...
space shuttle quality stuff ... man]. So in terminal, I moved the file
over to be foo.F90. Of course, MacVim notifies me that the foo.f90
files does not exist any more. So I ":q" that tab, and command-T for
a new tab.
Then I type ":e foo.F90" in the new tab, and the buffer appears blank,
with the file name listed as "foo.f90". Back to the lower cased
suffix. If I starte a new macvim session: $mvim foo.F90, it opens up
fine. Any insight? Some buffer voodoo?
I think you are running up against the case-insensitivity of Mac OS X
Extended FS. By default i believe most Macs are formatted as Mac OS X
Extended (Journaled). There is an option to create a Mac OS X Entended
(Case-sensitive, Journaled) partition.
This is not related to vim but the underlying FS.
in /tmp try this:
touch me ME
If you do a ls, you'll only see "me" and not "ME" and visa versa depending
on which filename you put first after the touch command.
This blew my mind too as I thought the Mac OS was UNIX at heart. If I'm
off base please let me know and tell me how I can fix my FS.
On Mon, Jun 11, 2012 at 12:29 PM, Srinath <srinath.vadlam...@gmail.com>wrote:
> These are 2 different files, but only the first loads.
Provided you're not actually on a HFSX Volume (which IIRC is still not the default) foo.F and foo.f are *one and the same*.
The default HFS+ is case-preserving which allows you to use upper- and lowercase letters in filenames but also will compare
them case-insensitive (thus foo.F == foo.f).
To see a world in a grain of sand, and a heaven in a wild flower,
hold infinity in the palm of your hand, and eternity in an hour.
-- Auguries of Innocence, William Blake