-
Notifications
You must be signed in to change notification settings - Fork 6
New command: activate #7
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
Comments
This would require spawning a new nested shell with an updated environment, and kerl makes no assumption on the shell being used. |
I see, I was afraid of that. There's no other shell trickery that can be used to avoid that? |
The only thing I can think of at the moment would be to allow the command only if you specified your favorite shell in you .kerlrc file, something like KERL_SHELL_COMMAND="/bin/bash" or whatever. |
It would create some nested shells, but that would be fine for me. If you want to avoid that you could just use the normal activation command. |
I want a new command,
activate
(or similar name) that activates a given installation:kerl activate r13b04
would callactivate
in the/Users/alind/Applications/erlang/r13b04
folder:The text was updated successfully, but these errors were encountered: