You never really want to get on IT’s radar anyway, because them looking closer at your work-issued gear tends to go in directions you didn’t anticipate (“Is that the approved wallpaper? Is Homebrew even approved? Are you running a web server on here?”). I may not get one until they sport Yosemite, though, and I don’t think they plan to upgrade the OS on this laptop. I’m nursing this work laptop, a 2010 MacBook Pro with Snow Leopard, along until I come due for one of the shiny new retina MacBook Pros with Mavericks. Then my stomach began to churn a bit, and I downloaded the MacVim source from GitHub, followed the build instructions, and got the same result. After the same system churn, of course, I got the same result.
#Install macvim install
Years of raising children has taught me that I can’t expect proper results without diligent monitoring, so I ran the install command again, but this time I watched it like a hawk, and actually expected different results.
My system churned a bit while I watched the github-issues.vim animated GIFs, and then reported: if_ruby.c:677: error: 'rb_encoding' undeclared (first use in this function) The simplest fix is to use terminal macvim as my system vim, so last Friday I opted for what I expected to be the easy route and typed: brew uninstall macvim brew install macvim -override-system-vim I always smile a bit at my nephew’s use of an extra-frowny mouth, but I also wince a bit to know that I’m letting this issue linger, rather than fix it. When I do, I see this: github-issues.vim requires Python support, sorry :c Although I usually edit files with (graphical) MacVim, I occasionally launch terminal vim.
0 kommentar(er)
