I tried to install vim from source. I do not have sudo rights.
So, i cloned the last revision from github, and configured as follows:
./configure \
--with-features=huge \
--enable-multibyte \
--enable-pythoninterp=dynamic \
--enable-python3interp=dynamic \
--with-python-config-dir=$PY_CONFIG \
--with-python3-config-dir=$PY3_CONFIG \
--enable-gui=gtk2 \
--enable-cscope \
--prefix=$HOME/.local $@
note the $HOME/.local prefix.
Then I did make && make install.
All went great. Now, unfortunately, when I try to take my first steps with vim, and do ~/.local/bin/vimtutor, It complains that it can't find the corresponding page:
Error detected while processing command line:
E484: Can't open file /usr/share/vim/vim74/tutor/tutor.vim
I am baffled how it thinks that I might have vim 7.4, and managed to mess up it's paths like that - because it installed the corresponding files, as was to be expected, in /home/simon/.local/share/vim/vim80.
Help? :D
Tips on whether I have not yet grasped how to build software like vim with make locally the right way, would be also very appreciated :) I'm new to the whole linux stuff...
Thanks a lot!
However, I am extremely curios to understand this: If I don't have it on my PATH,
$ which vimand$ which vimtutorreturn nothing; but when I call the binary directly, i.e.$ $HOME/.local/bin/vimtutor, it exhibits the erroneous behavior described in my OP.So, the PATH seems to be not only used by the shell to locate the binary, but also by vim to locate it's files? Anyone care to provide the rationale behind this behavior? Thanks! (I fear I will encounter it in other places too, and want to understand)
– simlei Apr 07 '18 at 17:00PATHto locate its files. Vimtutor usesPATHto locate a suitable vim, which maybe calledvimorgvimorvim74or ... (see the script for the full list of all the commands it looks for). So even if you don't have command namedviminstalled, vim might already be present on your system with a different name. – muru Apr 08 '18 at 00:44