Any help or information as to what is happening here would be appreciated. Unfortunately, even this custom build is showing this bug as well, meaning either transparency has to be disabled, or if it's actually a bug with MacVim itself. When opening any file in MacVim, whether from the terminal or via opening it within MacVim itself, Ma.
Opening macvim through terminal mac os x#
Instead, the custom MacVim loads it's runtime completely within it's Resources folder, i.e., in this case, it's set to load from ~/Applications/DevTools/MacVim.app/Contents/Resources/vim/.vim, as well as from the runtime within the Resources folder. Ive been seeing this happen frequently since I upgraded to Mac OS X 10.11 beta (Im on the 15A234d build at the time of writing this). I'm in the process of cleaning my vimrc and plugins, and I've built a separate MacVim, changing the headers so that by default, the custom MacVim will have a "sandboxed" runtime path, leaving the configurations in ~/.vim alone. Either way, my vimrc & plugin configurations are here. I'm not sure if it has to do with the transparency setting on my vimrc or not, or if it has to do with a deprecated method of rendering text in the beta of Mac OS X. Then I went to see the terminal, and boy was I surprised:
The text is "there" but only shown after you move through it: As in: no text is rendered, but MacVim knows it exists and will redraw the text when movement through it is made (see below:)
When opening any file in MacVim, whether from the terminal or via opening it within MacVim itself, MacVim will open with a completely see through window. I've been seeing this happen frequently since I upgraded to Mac OS X 10.11 beta (I'm on the 15A234d build at the time of writing this).
0 kommentar(er)
