MacVim on OSX / Yosemite: Editor windows do not appear at all

Installed MacVim on my Yosemite 10.10.2 Macbook Pro today from http://www.macupdate.com/app/mac/25988/macvim

The problem is that the editor windows (s) are not visible. If I open the file using the menu, it just won’t work: the editor window will not appear. It does not hide behind other windows, it is not listed in the Windows menu, it simply does not appear completely.

Strange, however, the file will appear in the MRU list. Thus, the entire editor is completely useless. Should I just build gvim myself? Is this application really supported by anyone?

+6
macvim osx-yosemite macos
source share
4 answers

I would read a few answers that suggest running:

brew install macvim 

... does the trick.

You might want to try this first.

What worked for me ...

However, this did not work for me, because although he updated my macvim, the one associated with the / Applications folder was not the version updated by brew .

So, here are the steps I had to take.

  • Close MacVim if it is open.
  • Delete MacVim file in / Applications.
  • In the terminal, run:

     brew install macvim --override-system-vim 
  • Run (this will add a link to your application file):

     brew linkapps macvim 

I'm not sure that every step above is required or the --override-system-vim flag is required, but I can say that following the steps above worked for me.

Hope this helps.

+11
source share

It seems that the development of MacVim has been ported to a new repository (and perhaps another development group?):

https://github.com/macvim-dev/macvim

This repo has been updated to fix MacVim's graphical issues in Yosemite. (This is the same location that the macwim brew formula is currently extracting the source code, so MacVim runs on Yosemite when installed via brew.)

They also have a set of precompiled binary releases:

https://github.com/macvim-dev/macvim/releases

The latter (β€œ image 76 ”) worked fine for me in Yosemite. You just need to download the .tbz archive, double-click it to unzip it into a folder, and then drag the MacVim.app icon into applications - much easier and less invasive than installing the entire package management system and creating an environment! :)

Note. I had to execute the command specified in https://stackoverflow.com/a/3/9778/ to correct the display errors displayed in full screen for snapshot 76:

 $ defaults write org.vim.MacVim MMNativeFullScreen 0 
+4
source share

Today I have the same problem.

Decision:

 mv ~/.vimrc ~/.vimrc_bak 

There seems to be something wrong with my .vimrc file.

+1
source share

I had the same problem and one of the answers here helped me, but not because of an explanation, so I thought it might be useful to others.

Some plugins may depend on vim version and may work in version 7, but not in version 8, when you install MacVim, it may be version 8, and the vim terminal version may be 7, both will use them. vim and .vimrc to load plugins and configuration, when you open vim from the terminal, it can still work, because the plugins are dependent on vim version 7, but when you try to run MacVim, it will try to load plugins using version 8 and then it will work, the reason is that some of the answers worked because they replace the vim system, so MacVim and vim will be in the same major version, if you upgrade the previous version, you can do this to clear and then download MacVim or vim and check that everything works and then add Upaite to use plug-ins one by one, making sure that they do not violate vim. At least with this method, I found that one of the plugins does not work as expected, and its removal solved the "MacVim" problem.

In short: - move your .vim as .vim_bak - move your .vimrc as .vimrc_bak (suggested by @hai feng kao)

And test if this solves the problem, if in this case the plugin breaks your installation and you will need to activate some and find out what exactly is causing the problem.

Hope this helps others, I followed many of these recommendations without success, until I decided to update vim (terminal), and that too started to break, which was pointing me in the right direction.

Again hope this saves a few hours for some.

0
source share

All Articles