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

Command 'activate' doesn't looks like a valid VenGO command. #8

Open
st0nx opened this issue Jul 7, 2016 · 13 comments
Open

Command 'activate' doesn't looks like a valid VenGO command. #8

st0nx opened this issue Jul 7, 2016 · 13 comments

Comments

@st0nx
Copy link

st0nx commented Jul 7, 2016

The manual you wrote, use command "vengo activate [name]" to activate enviriement, but is command not working. I run from ubuntu command line.

@DamnWidget
Copy link
Owner

It is vengo_activate it is a separate bash script.

@st0nx
Copy link
Author

st0nx commented Jul 7, 2016

user@user-linux:~$ vengo mkenv -g go1.6.2 config_env
Checking installed Go versions... Pulling Go sources from Github... ✔
✔
Checking manifest integrity... ✔
Go config_env environment created using go1.6.2
user@user-linux:~$ vengo activate config_env
Command 'activate' doesn't looks like a valid VenGO command...
suggestion: execute 'vengo' with no arguments to get a list of valid commands
user@user-linux:~$ vengo_activate config_env
check_environment_exixtance: command not found

Maybe, I do something wrong.

@DamnWidget
Copy link
Owner

Can I know which SHELL do you use and how do you enable vengo in your system?

@st0nx
Copy link
Author

st0nx commented Jul 8, 2016

I used standart linux ubuntu terminal.

@DamnWidget
Copy link
Owner

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 .bashrc file just below the source $HOME/.VenGO/bin/vengo line.

@st0nx
Copy link
Author

st0nx commented Jul 8, 2016

Thank you! It works.

@dixudx
Copy link

dixudx commented Jul 13, 2016

$ 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.

@DamnWidget
Copy link
Owner

What is the value of your $VENGO_HOME environment variable?

@dixudx
Copy link

dixudx commented Jul 13, 2016

$ echo $VENGO_HOME
/home/ubuntu/.VenGO

@DamnWidget
Copy link
Owner

DamnWidget commented Jul 13, 2016

Well, for some reason your SHELL is failing to find $VENGO_HOME/MyEnv (the function is implemented here), I will try to drop that SHELL session and start a new one.

@dixudx
Copy link

dixudx commented Jul 13, 2016

It is so weird that I can't find the folder $VENGO_HOME/MyEnv. However I can list the envs.

@DamnWidget
Copy link
Owner

VenGO works with the following paths on Linux:

  • ~/.VenGO
  • ~/.cache/VenGO

The only difference between the lsenvs and the vengo_activate commands is that the lsenvs is executed by Go (using os.Getenv) and vengo_activate is a shell script.

Is even weirder when you think about Go inheriting the environment data from the shell session that it is being executed on.

@dixudx
Copy link

dixudx commented Jul 13, 2016

After manually delete /home/ubuntu/.cache/VenGo, reinstall Go 1.2.2 and the corresponding env. I can successfully activate the virtual env.

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

3 participants