I am quite new to Vim on Mac OSX 10.13. I installed a few plugins, especially for use with Python.
Thus I installed YouCompleteMe & compiled it. Originally I got an error because a trial of Kite shut the server down. But this I deactivated and now I restart and restart the server just to get it shutdown.
And the YcmToggleLogs does not show anything :-(
I followed all of the advice given here: YCM error. The ycmd server SHUT DOWN (restart wit...the instructions in the documentation
But still it doesn't work.
And of course I followed along with the official install manual:
Install YCM plugin via Vundle
Install cmake, macvim and python
Note that the system vim is not supported.
brew install cmake macvim python
.
Install mono, go, node and npm
brew install mono go nodejs
Compile YCM
cd ~/.vim/bundle/YouCompleteMe python3 install.py --all
Btw, when compiling everything I get several warning along these lines:
ld: warning: text-based stub file /*****/CoreFoundation.tbd and library file
/****//CoreFoundation.framework/CoreFoundation are out of sync.
Falling back to library file for linking.
Any ideas what I can do to get it off the ground?
Thanks.
On Linux, with VIM >8.1
To solve the issue, run the installer from the plugin.
Go to vim folder
cd ~/.vim/plugged/YouCompleteMe
and run the installer.sh
./installer.sh
hope this solution solves your as well.
Related
I'm trying to install Kieran Healy's Emacs Starter Kit (https://github.com/kjhealy/emacs-starter-kit) on linux arch (I have also tried on a Mint installation, running into the same errors), but I'm having quite some trouble.
After deleting my ~/.emacs.d and installing the starter kit, emacs starts installing packages, but runs into a 'Package magit- is not available'-error. Other Melpa-packages are installing fine. An m-x refresh-contents doesn't make a difference, and neither does an m-x install-package magit.
I am able to install magit if I temporarily rename my .d.emacs and run with a fresh .emacs, and if I, after installation of magit, enable the starter kit again, emacs will load the installed magit-package perfectly fine. It does stall again, on several other packages (ipython, typopunct), in exactly the same manner.
If I comment out the 'require of these three packages, installation seems to work, but stalls on a not found 'ob-shell (as in this question: https://emacs.stackexchange.com/questions/21366/should-i-have-removed-shell-t-to-clear-an-ob-shell-initialization-error). This is in addition to several other errors that seem to indicate a not-complete installation as I try to continue use of emacs.
I have not been able to find any documentation relating to this. Appearently, missing packages are not uncommon with old emacs-installations, but as I am using a 25.1.1 install, this does not seem to be the problem.
Any ideas going forward?
The issue with magit was indeed solved a little while ago. The issue with ipython that apc raised exists because that's a package from the Marmalade repo, which needs to be added manually to the list of repositories. To install it, just execute the following code in the console.
M-x package-refresh-contents [RET]
M-: (add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/"))
M-x package-refresh-contents [RET]
M-x package-install [RET] ipython
I installed Vim 7.4 in a Windows 8 machine and it was working fine. After installing all plugins in my .vimrc, GVIM crashed and it wouldn't open again. I could manage to use VIM from cmd but not without some errors. My first try was to reeinstall GVIM completely. After reinstalling, it worked fine but if I also reinstall my plugins it would crash and not open again. What should I do?
I removed all plugins and installed one by one until I got the error, which was with the Ultisnips plugin. I happen to know that this plugin requires VIM with Python support, which my VIM probably wouldn't have. To test this, run vim --version and look for a +python (or run echo has("python") from inside GVIM and look for a output of 1). In my case, it was -python, which was confusing, since I have Python installed. According to this answer, you need to install Python after installing VIM, so I did it and it worked.
I'm using RVM (1.17.7) and Ruby 1.9.3p362. In the long run I want to move over to Vim in the Terminal with Tmux. I'm trying to learn how to install and run with my choices for plugins instead of defaulting to Janus, just trying to learn it all and not be a cargo cult programmer.
I did a brew install of Vim git clone of Command-T (I'm using Pathogen) while the Ruby was set to 1.9.3... and everything is good in Terminal using Vim and Command-T. When I run :ruby puts RUBY_VERSION in Terminal Vim, it gives 1.9.3 back. The Command-T works fine too.
When I try and use the same Command-T in MacVim it crashes and the Terminal says:
Vim: Caught deadly signal SEGV
Vim: Finished.
I did a brew install macvim while in 1.9.3, but when I launch mvim from Terminal and run :ruby puts RUBY_VERSION I get back 1.8.7. I know Wincent recommends the system version of Ruby for installing Command-T and I've read you have to match up the Ruby version either way. I've managed to get it working for both when I had the system ruby, but can't get it for both on the RVM version with 1.9.3...
Is it possible? Should I just forget about MacVim and stick with Vim in the Terminal?
Other things I thought I could do would be to have a disabled folder and just move the different Command-T installations in and out of it. Or maybe do an if for 'gui_running' and target the different installs. Any advice to set me straight would be great.
I've installed Tim Pope's rvm.vim and can set the Ruby version, but that doesn't seem to stop the crash in the MacVim when I call :CommandT.
I'm guessing that you installed the macvim package before you installed installed all the rest of that, and then installed the vim package afterwards. That'd explain why it works in terminal mode. These are two different packages, and they have their own build options.
Run:
vim --version
And compare the output to:
mvim --version
In particular, check out the last line (starts with Linking:). You'll probably see ruby-1.8 linked in for mvim, and ruby-1.9.1 linked in for vim (note that 1.9.3 reports 1.9.1; it's the C API version, not the Ruby version).
If all this is true, fix it by doing:
brew uninstall macvim
brew install macvim
It should build against your 1.9.3 config. Make sure rvm current reports 1.9.3 before you do that.
I'm trying to install CommandT for Vim on Windows. My setup:
OS: Windows 7
Vim: Cream installation of Vim (Vim 7.3 plus ruby support)
Ruby: rubyinstaller-1.8.7-p334.exe
Ruby dev kit: DevKit-tdm-32-4.5.1-20101214-1400-sfx.exe
I followed this guide http://rfbrazier.posterous.com/installing-the-command-t-vim-plugin-on-window, as well as the official CommandT installation screen cast. I've installed ruby and the dev kit successfully, and have verified the dev kit installation by installing the discount gem.
My problem is that when I try to generate the CommandT makefile, I get an error saying the script can't find ruby.h: "checking for ruby.h... no". No makefile, no CommandT :(
Any advice?
I had this problem too. Download http://rubyforge.org/frs/download.php/66888/devkit-3.4.5r3-20091110.7z and install it according to INSTALL.txt from this 7z-file
If you are using gVim 7.2 on windows and want a Command-T bundle with the extension already compiled, get from the same source I use in my vimfiles repository: https://github.com/carlosedp/vimfiles/tree/master/bundle
I wanted to use cscope enabled vim - unfortuantely , the binaries at work are not compiled with cscope support , and when I tried building from src , I'm getting a lot of errors due to proper dev packages not being installed.
So , does anyone have a link where I can a precompiled binary with cscope support ? Btw , I'm using linux.
Just build your own vim binary from source code maybe a good solution ^_^
wget ftp://ftp.vim.org/pub/vim/unix/vim-7.2.tar.bz2
tar xjf vim-7.2.tar.bz2
cd vim72
./configure --enable-cscope
make && make install
You will get a cscope supported vim 7.2
Not quite an answer to your request for a pre-compiled vim 7.2, but you said part of your compiling problems is that you "don't have the privileges for installing reqd packages" (in you comment to #chenkaie's answer). If the other reqd packages use configure, you can compile them to install into a directory you have control over, like this:
./configure --prefix=/dir/with/permissions
make && make install
configure-based installers support the --prefix switch, which results in the installed packages in locations like <prefix>\bin, <prefix>/lib, etc. With this trick you may be able to build all the reqd packages in order to build vim 7.2 itself.
If the reqd packages are not configure-based, you might want to look at the installer (makefile?) of the reqd package to see if it has an option similar to configure --prefix=<dir>
I have the default package Ubuntu gives me from doing an 'apt-get install vim', vim_1%3a7.1-138+1ubuntu3.1_i386.deb.
Inside of vim, when I type
:echo has('cscope')
it prints
1
as expected.
Granted, you do say you are looking for Vim 7.2 I don't know what improvements 7.2 has seen over 7.1, but it looks like there are still build problems with 7.2 that are being hammered out. I'd suggest just using 7.1 for the time being.