From 63223110e8ba449cd79d070cbf5acdac89033e0e Mon Sep 17 00:00:00 2001 From: stephenhsu Date: Thu, 14 Jul 2016 13:17:58 +0800 Subject: [PATCH] fix outdated info of README --- README.md | 10 ++++++---- bin/includes/env | 2 +- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index e17c91a..ee5cb17 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,8 @@ curl -L https://raw.github.com/DamnWidget/VenGO/master/install.sh | bash Finally the command below will enable the `vengo` command in your system ``` -$ source $HOME/.VenGO/bin/vengo +$ source $HOME/.VenGO/bin/vengo.sh +$ source $HOME/.VenGO/bin/includes/* ``` #### 3 Optional @@ -64,7 +65,8 @@ If you want to enable `vengo` in permanent basis in your system, you can add it files like ``` -echo "source $HOME/.VenGO/bin/vengo" >> $HOME/.bashrc +$ echo "source $HOME/.VenGO/bin/vengo" >> $HOME/.bashrc +$ echo "source $HOME/.VenGO/bin/includes/*" >> $HOME/.bashrc ``` #### Fish users @@ -112,11 +114,11 @@ $ vengo mkenv -g go1.2.2 MyEnv This will create a new isolated environment that uses go1.2.2 and uses `$VENGO_HOME/MyEnv` as `GOPATH` -To activate this new environment thw programmer just have to use `vengo activate` with the name of the recently created +To activate this new environment thw programmer just have to use `vengo_activate` with the name of the recently created environment ``` -$ vengo activate MyEnv +$ vengo_activate MyEnv ``` Now, whatever is installed using `go get` will be installed in the new isolated virtual go environment. It's `GOPATH` bin diff --git a/bin/includes/env b/bin/includes/env index 03ab586..60c05b0 100644 --- a/bin/includes/env +++ b/bin/includes/env @@ -22,7 +22,7 @@ function check_environment_exixtance { environment="$1" if [ ! -d "$VENGO_HOME/$environment" ]; then echo "VenGO: Environment '$environment' doesn't exists." >&2 - suggest "try to create it with 'vengo create $environment -g '" >&2 + suggest "try to create it with 'vengo mkenv -g $environment'" >&2 return 1 fi return 0