.vimrc not sourced

[GoogleCodeExporter]

IMPORTANT! Before creating a new Issue please search the old Issues for 
duplicates.  Also, 
please do not use this page to ask questions, instead post to the vim_mac 
mailing list.  There are 
more people on that list that can answer questions.  Only file an issue if you 
have found a bug.  
(You can safely delete this text now that you have read it and enter an issue 
report.  Thank you 
for taking the time to report new bugs!)

What steps will reproduce the problem?
Opening MacVim

What is the expected output? What do you see instead?
Not sourcing .vimrc

What version of MacVim and OS X are you using (see "MacVim->About MacVim" and  
"Apple 
Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6 Intel")?
Snapshot 49, 10.5.8 Intel

Please provide any additional information below.
.vimrc is there, and sourced fine in all previous versions

Original issue reported on code.google.com by jack.sta...@gmail.com on 18 Aug 2009 at 1:00

[GoogleCodeExporter]

I'm afraid you'll have to provide a lot more information than this in order for 
me to
help you.

1. Are you 100% sure this only started happening with snap 49?
2. Are you 100% sure that .vimrc is not getting sourced?

If the answer is "yes" to either question, then exactly how did you come to this
conclusion?

Original comment by bjorn.winckler@gmail.com on 20 Aug 2009 at 9:06

[GoogleCodeExporter]

I can second this problem: a coworker downloaded MacVim 7.2 stable 1.2 (33.3) 
on Snow Leopard 10.6.2, and 
has made many cosmetic changes to .vimrc, all of which appear in a vi/vim 
terminal but not in MacVim.  I had 
read a report that copying the file to .gvimrc might fix this, but it does not 
in this case.

Original comment by john.des...@gmail.com on 17 Dec 2009 at 3:51

[GoogleCodeExporter]

What does Vim respond with when you type

:echo $VIM
:echo $HOME
:echo $MYVIMRC
:echo $VIMINIT

(one at a time) inside MacVim?  What if you do the same inside Vim?

Does vimrc get sourced if you start MacVim without the GUI?  I.e. start from 
Terminal with

/Applications/MacVim.app/Contents/MacOS/Vim

Original comment by bjorn.winckler@gmail.com on 17 Dec 2009 at 3:58

[GoogleCodeExporter]

The user reports the following results:

echo $VIM
inside MacVim
            /Applications/MacVim.app/Contents/Resources/vim
inside Vim (terminal window)
            /usr/share/vim
:echo $HOME
inside MacVim
            /Users/benkov
inside Vim (terminal window)
            /Users/benkov
echo $MYVIMRC
inside MacVim
            /Users/name/.vimrc
inside Vim (terminal window)
            /Users/name/.vimrc
echo $VIMINIT
inside MacVim
            (nothing appears
inside Vim (terminal window)
(nothing appears)

Also see the attached error trace, which implies a bad simlink or MacVim 
bundle.  I don't think either is the 
case here.

Original comment by john.des...@gmail.com on 17 Dec 2009 at 4:44

Attachments:

• macvimerr-1.txt

[GoogleCodeExporter]

The error in the log file seems to indicate that the user is starting MacVim 
the "wrong way" (are you absolutely 
certain that no symlinking is involved?).

Does the problem appear if MacVim is started by double-clicking the MacVim icon 
in Finder?

Does it appear if started from Terminal with the command

/Applications/MacVim.app/Contents/MacOS/Vim -g

?

Original comment by bjorn.winckler@gmail.com on 17 Dec 2009 at 4:49

[GoogleCodeExporter]

Latest reports from this user below ... maybe you'll catch a problem that I 
don't see.  I've asked for results of 
'Vim -g' command and will post those ASAP.
Also attached is a listing of /usr/share/vim*, which doesn't include any sym 
links (though that doesn't 
conclusively prove that there are no links anywhere).
========
Transferred MacVim app and mvim to Applications directory,  deleted the rest of 
the new MacVim-7_2-
stable-1_2 directory (including the directory itself) and no matter how I 
double click MacVim.app it does not 
open.  I recreated the MacVim-7_2-stable-1_2 directory in the /Applications 
directory and now MacVim 
opens on a double click.  However, neither MacVim nor VI on the terminal window 
are reading the .vimrc file 
in my root directory – the colors are all defaults. 
...
Status is now macvim and vi on a terminal window use the default color scheme 
– can’t find out what file I 
have to edit/create to change the LineNr colors.

Original comment by john.des...@gmail.com on 18 Dec 2009 at 2:06

Attachments:

• usrvimdir.txt

[GoogleCodeExporter]

It sounds to me like the user is creating an alias inside /Applications instead 
of actually dragging the app into 
that folder.  The MacVim-7_2-stable-1_2 directory has nothing to do with 
whether MacVim starts or not.

To avoid any potential installation errors, try this:

1. Download the latest snapshot (which is better than stable build)
2. Unzip the archive which just downloaded by double-clicking on it (unless it 
was automatically unzipped by 
the browser)
3. Open the folder starting with MacVim, inside this folder is the MacVim icon, 
double-click that

Once this is done and the user can confirm that MacVim at least opens, try this:

1. In MacVim, enter ":e ~/.vimrc"
2. Add the line "colorscheme elflord"
3. Save and quit MacVim
4. Restart MacVim, the colorscheme should now be "elflord"

This really really should work...

Original comment by bjorn.winckler@gmail.com on 18 Dec 2009 at 2:21

[GoogleCodeExporter]

Sorry for the delay.  The person I'm trying to help will give this a try as 
soon as possible.

Original comment by john.des...@gmail.com on 23 Dec 2009 at 2:11

[GoogleCodeExporter]

It looks like clearing out the previous cruft and reinstalling with the latest 
snapshot has cured all ills in my user's 
case.  Thanks for your help and patience, Bjorn.

Original comment by john.des...@gmail.com on 23 Dec 2009 at 4:44

[GoogleCodeExporter]

I'm glad you sorted it out.

Original comment by bjorn.winckler@gmail.com on 23 Dec 2009 at 4:51

• Changed state: Invalid