Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
vim_mac
Home
+ new post
About this group
Join this group
weird behavior with .f90 and .F90 files
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   6 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Srinath  
View profile  
 More options Apr 20 2012, 5:23 pm
From: Srinath <srinath.vadlam...@gmail.com>
Date: Fri, 20 Apr 2012 14:23:32 -0700 (PDT)
Local: Fri, Apr 20 2012 5:23 pm
Subject: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author
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?

Btw..thanks for all the help.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Srinath  
View profile  
 More options Jun 11 2012, 3:29 pm
From: Srinath <srinath.vadlam...@gmail.com>
Date: Mon, 11 Jun 2012 12:29:01 -0700 (PDT)
Local: Mon, Jun 11 2012 3:29 pm
Subject: Re: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author

Bumping since I never got a response.

Do this:

mvim foo.F

type: foo.F in file (save and close).

mvim foo.f

type: foo.f in file (save and close)

then run mvim -d foo.F foo.f

These are 2 different files, but only the first loads.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Xiao G. Wu  
View profile  
 More options Jun 11 2012, 4:59 pm
From: "Xiao G. Wu" <xiao...@gmail.com>
Date: Mon, 11 Jun 2012 13:59:49 -0700
Local: Mon, Jun 11 2012 4:59 pm
Subject: Re: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author

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:

--
+xiaogwu <https://plus.google.com/107773553434423282536>
xiao...@gmail.com
(415) 891-9426 (GV)

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
René Köcher  
View profile  
 More options Jun 11 2012, 3:38 pm
From: René Köcher <shir...@gmail.com>
Date: Mon, 11 Jun 2012 21:38:05 +0200
Local: Mon, Jun 11 2012 3:38 pm
Subject: Re: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author

Am Montag, 11. Juni 2012 um 21:29 schrieb Srinath:

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).

Cheers,

--
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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Srinath  
View profile  
 More options Jun 12 2012, 12:14 pm
From: Srinath <srinath.vadlam...@gmail.com>
Date: Tue, 12 Jun 2012 09:14:50 -0700 (PDT)
Local: Tues, Jun 12 2012 12:14 pm
Subject: Re: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author

I have a case sensitive system.

Running vim in Terminal does the correct thing.

So, the file system case sensitivity is not the issue.

Any other ideas?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
björn  
View profile  
 More options Jun 12 2012, 12:32 pm
From: björn <bjorn.winck...@gmail.com>
Date: Tue, 12 Jun 2012 18:32:40 +0200
Local: Tues, Jun 12 2012 12:32 pm
Subject: Re: weird behavior with .f90 and .F90 files
Print | Individual message | Show original | Report this message | Find messages by this author

On Tue, Jun 12, 2012 at 6:14 PM, Srinath wrote:
> I have a case sensitive system.

> Running vim in Terminal does the correct thing.

> So, the file system case sensitivity is not the issue.

> Any other ideas?

You may have to build a custom binary.  Take a look at the discussion
titled "case insensitivity on hfsx" in the archives:

http://groups.google.com/group/vim_mac/browse_thread/thread/b2aa9fb76...

Björn


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google