What should I do to work vim again?

Question

make test from inside .. / vim / src seems to have disabled vim. I also can not recompile the source code.

What should I do to work vim again?

Longer Explanation:

From the terminal on Mac OSX 10.10.4. I tried to reconfigure vim to include copy / paste capabilities from my system clipboard, as well as enable python3 encoding.

The vim code was compiled from the source that I cloned from the git repository.

 git clone https://github.com/vim/vim.git 

I also installed it so that my version of vim runs instead of the system vim by adding the following to my .bashrc file

 alias vim='/the/path/to/my/version/of/vim' 

After setting up my team. / configure I ran it as follows.

 ./configure --with-features=huge --enable-perlinterp=yes --enable-pythoninterp=yes --enable-python3interp --enable-multibyte --enable-gui=auto --with-x make make install 

from vim that I printed

 echo get('python3') 

and was glad to see "1" indicating that I now have python3 support.

However, when I asked for the command line version

 vim --version 

I saw that xterm_clipboard is still not included.

I hunted a little more and saw a make test offer on the python3 install page. I did this, still from the .. / vim / src folder, and it went on for a couple of minutes, sometimes with bright red errors. Then I tried to open vim, but received the following error message, followed by a prompt:

 vim -bash: /mypath/../src: is a directory 

So, I did git pull and recompiled from source without error messages. However, vim still could not be opened, with the same error message.

 command -v vim 

gave the path to vim that I previously assigned in my .bashrc file.

Answer 1

The simple answer if vim does not work is to start a new shell, especially after updating the .bashrc file. Updates to the .bashrc file apply only to future bash sessions.

Lessons learned:

I shouldn't have done

 make test 

When recompiling from code, use

 make clean 

Caveat In the end, it is possible that an attempt to install macvim via brew (failed due to a conflict with macports) is what solved the problem, because it was after this attempt (and in a new session) that I was able to open vim again.