Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt-vim continually looking for python in /usr/bin/env #58

Open
caleywoods opened this issue Jun 14, 2018 · 2 comments
Open

apt-vim continually looking for python in /usr/bin/env #58

caleywoods opened this issue Jun 14, 2018 · 2 comments

Comments

@caleywoods
Copy link

caleywoods commented Jun 14, 2018

I am working from a Samsung Chromebook 3 running what is similar to an ubuntu chroot via crouton. I have python 3.5 located at /usr/bin/python3.5 and it's aliased in my .bashrc with alias python='/usr/bin/python3.5 and executing python --version from the bash shell will return back the python version.

When trying to install NERDTree with apt-vim, here is the output:

(xenial)caley@localhost:~$ apt-vim install -y https://github.com/scrooloose/nerdtree.git
/usr/bin/env: 'python': No such file or directory

If I prefix the above apt-vim install command with python then everything works fine. Should I modify .vimpkg/bin/apt-vim to point to /usr/bin/python3.5 or is there a better solution for this?

@egalpin
Copy link
Owner

egalpin commented Jun 19, 2018

The better solution is probably for me to make apt-vim installable via pip, homebrew, and various linux package managers (yum, apt-get, etc) such that this is handled correctly.

Your initial thought to modify the apt-vim python script to point to /usr/bin/python3.5 would rectify this on your system :-) I can also probably modify the install script to try to handle this more gracefully (i.e. find the system python via which python and add that as the shebang at the top of apt-vim)

@caleywoods
Copy link
Author

Yeah, the change at the top of the file took care of it for me locally. apt-get should also work at least in my case, that seems to be how packages are installed inside the chroot, some kind of mock ubuntu CLI only type setup since I didn't opt for a window manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants