I have a error when i use vim. After I place this line in .vimrc
Plugin 'Valloric/YouCompleteMe'
and
:PluginInstall
error:
YouCompleteMe unavailable:
My vim : VIM - Vi IMproved 7.3
Anyone's know how to fix it ?v
The :version command tells you the exact Vim version. If you grabbed the official installer from vim.org, you probably have 7.3.000. As Vim 7.4 has been released, it's the easiest to upgrade to that version.
If you have the problem with Homebrew version on Mac, try the following as officially documented. Please make sure you're running vim not vi on your mac.
cd ~/.vim/bundle/YouCompleteMe
./install.sh
Related
I started using vim earlier this summer and have recently started to add plugins. Todays challenge is to install YouCompleteMe.
Problem: During the installation process I noticed that my vim version (7.4) doesn't have support for python/python3.
Question: How can I fix this without messing up all my plugins/.vimrc file?
Will a clean install even affect my plugins/.vimrc?
I read some where that I should install 'vim-nox'.. Should I?
My setup: Ubuntu 16.04. Vim 7.4. Plugins are installed via Pathogen.
Thanks in advance for your replies!
Kind regards, Edvin
As long as your plugins are installed in $HOME/.vim (or MsWindows equivalent), and not into /etc/vim or /usr/share/vim, there should be no problem: you can upgrade your vim version without impacting what you have already installed.
See :h 'rtp' and :h startup.
Plugins and vimrc are just files. They can't be executed stand alone. Further, they come into power, only when vim is running.
So, your uninstallation/installation of vim doesn't change/affect plugins or vimrc. However, if the plugin or vimrc has code related to specific environment (like OS, terminal, etc,.) or needs specific features of vim and if your new version doesnt support them, you may have problems. Plugins in default folder(where vim is installed) will get deleted when you uninstall. The plugins in HOME directory aren't affected anyway.
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.
So i'm rocking a VIM version 6.3.82 on rhel 4.9... which i'd imagine is the biggest culprit. (no chance of an upgrade any time soon)
I downloaded the latest Rails.vim and have installed this many times on my home machine.
I try the command :Rails! and i Get "e493: Not an editor command."
In my .vimrc i've added
set nocompatible
syntax on
filetype plugin indent on
Am i doomed with a dated vim to use most any plugins? Am i missing something in my .vimrc to enable vim plugins?
Any direction is appreciated. :p-
TIA,
Kirby
You'll need to use an old version of Rails.vim it looks like. The last version that worked with Vim 6 is version 2.1:
http://www.vim.org/scripts/script.php?script_id=1567
You may be able to compile your own version of vim in your home directory if you want to use the latest Vim and Rails.vim.
I am trying to install commandT plugin and vim 7.3 has no ruby support and i am a newbie to vim. i don't think i know how to complile ruby support myself. If i go back to vim 7.2 will i be missing out on anything that 7.3 has to offer?
Once you have installed Vim 7.3 you can find all the details about the changes since Vim 7.2 with:
:help version-7.3
Persistent undo is really nice, it would be a shame to live without that.
If you're running vim for Windows you could try installing Cream, from here: http://www.vim.org/download.php#pc. That package contains vim 7.3 plus ruby support plus other goodies.
relativenumber is working really well for me.