-
Notifications
You must be signed in to change notification settings - Fork 11
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
Command 'activate' doesn't looks like a valid VenGO command. #8
Comments
It is |
Maybe, I do something wrong. |
Can I know which SHELL do you use and how do you enable vengo in your system? |
I used standart linux ubuntu terminal. |
Ok, so I guess you are using BASH, try do this and give a try: source ~/.VenGO/bin/includes/* If it works put that line in your |
Thank you! It works. |
$ vengo list
Pulling Go sources from Github... ✔
Installed
go1.2.2 ✔
$ vengo mkenv -g go1.2.2 MyEnv
Checking installed Go versions... Pulling Go sources from Github... ✔
✔
Checking manifest integrity... ✔
Go MyEnv environment created using go1.2.2
$ vengo lsenvs
Virtual Go Environments
MyEnv go1.2.2 ✔
$ source ~/.VenGO/bin/includes/*
$ vengo_activate MyEnv
VenGO: Environment 'MyEnv' doesn't exists.
suggestion: try to create it with 'vengo create MyEnv -g <go_version>' Still unable to activate the virtual env. |
What is the value of your |
$ echo $VENGO_HOME
/home/ubuntu/.VenGO |
Well, for some reason your SHELL is failing to find |
It is so weird that I can't find the folder |
VenGO works with the following paths on Linux:
The only difference between the Is even weirder when you think about Go inheriting the environment data from the shell session that it is being executed on. |
After manually delete |
The manual you wrote, use command "vengo activate [name]" to activate enviriement, but is command not working. I run from ubuntu command line.
The text was updated successfully, but these errors were encountered: