The advice that would probably fix most people's problems when they're getting a segfault is to try putting their system python first on their PATH when compiling ycm_core.
sys.version isn't specific enough and sys.executable outright lies sometimes), the user needs to make the call. Unless there's a way to reliably determine which python is being used by vim (and I haven't been able to figure out a reliable way. I think that it just needs to be made clear that YCM is going to compile against whatever python (and python-config, which should match) it finds in the PATH. Many users won't have some other python installed (but some will). setlocal can change setting of current buffer. nnoremap x dd is a bad habit, in local buffer you shoul use. nnoremap d dd nnoremap x dd x mapping will only take effect in current buffer.
So as it stands, the majority of MacVim users will have a MacVim linked against system python (but some won't). to force you use shortcut, map occord keys to. The binary MacVim distribution, of course, always links against system python. This will likely get fixed at some point (either by a workaround in the homebrew formula or better detection by MacVim at compile time).
Macvim flags how to#
Homebrew-MacVim also uses system python (unless the user figures out how to link it against a different one, with the symlinking hack or some other way). I fixed this using the symlinking hack (referenced by pencilcheck just above). However, my MacVim (which I'd compiled by hand) was using my system python. I had python installed as a framework under /Library (from some installer, I forget), which was the python that the ycm_core installer discovered (correctly, due to xgalaxy's python_finder fix). This isn't particular to homebrew in any way.
I think that the FAQ item regarding this is still not as helpful as it could be.
0 kommentar(er)
