Permalink
Browse files

remove `ry export` - it's superceded by new `ry setup` semantics

you can use `eval "$(ry setup <name>)"` to activate a specific ruby in
your shell.
  • Loading branch information...
1 parent d612dee commit 90e5aecb4a781a8a2657a1182cf4d9c1bacdb783 @jneen committed Mar 18, 2012
Showing with 0 additions and 14 deletions.
  1. +0 −14 bin/ry
View
14 bin/ry
@@ -250,17 +250,6 @@ ry::fullpath() {
}
#
-# ry export <name>
-# Print a sh-evaluable bash snippet that export $PATH as the
-# fullpath for the given ruby.
-#
-ry::export() {
- local name="$1"
- assert_installed "$name"
- echo "export PATH=`ry fullpath "$name"`"
-}
-
-#
# ry exec <name>[,<name2>[,...]] <command...>
# execute the given command in the context of the given rub{y,ies}
#
@@ -330,9 +319,6 @@ ry::usage() {
includes the given ruby's path.
If no name is given, uses the \`current\` symlink
- ry export <name> Print a sh-evaluable snippet that sets \$PATH to
- \`ry fullpath <name>\`.
-
Options:

0 comments on commit 90e5aec

Please sign in to comment.