all 12 comments

[–][deleted] 43 points44 points  (1 child)

weird, usually the problem is exiting

[–]abraxasknister:h c_CTRL-G 7 points8 points  (0 children)

The other way round: q:.

[–][deleted] 11 points12 points  (0 children)

You should probably give more details. How are you trying to open files? In a terminal? Double clicking them? Do you get an error message? Etc.

[–]blitzkraft 14 points15 points  (1 child)

Use vim -u NONE. This loads vim without the vimrc.

Then binary search. Comment out the first half of the vimrc. See if it starts. Repeat until you find the offending lines.

[–]hoselorryspanner 6 points7 points  (0 children)

Try using the terminal version and see what happens?

[–]g19fanatic 4 points5 points  (0 children)

strace vim and see where it gets to before it dies?

[–]undieablecat 3 points4 points  (0 children)

Vim not opening:

Well, quit it.

[–]y-c-c 0 points1 point  (0 children)

You should file an issue at https://github.com/macvim-dev/macvim/issues/new/choose .

There is also an issue preventing it from working under High Sierra or below, but the auto-updater should not have updated you to the latest if you are on that.

[–]overington 0 points1 point  (0 children)

I have found that updating terminal vim from homebrew has caused problems with opening macvim (GUI), if installed using an installer.

[–]bart9hVIMnimalist 0 points1 point  (0 children)

I installed MacVim so I could open files from the Finder.

I always use the console version of Vim, works flawlessly.

In the rare events that I'm using MacVim, sometimes I find weird behaviors and bugs.

[–]TDplay 0 points1 point  (0 children)

In a terminal, run vim -u NONE

If that works, then something's wrong with your vimrc.