Skip to content

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

Open
eproxus opened this issue May 31, 2011 · 4 comments
Open

New command: activate #7

eproxus opened this issue May 31, 2011 · 4 comments

Comments

@eproxus
Copy link

eproxus commented May 31, 2011

I want a new command, activate (or similar name) that activates a given installation:

$ kerl list installations
r14b03_hipe_native /Users/alind/Applications/erlang/r14b03_hipe_native
r13b04_hipe /Users/alind/Applications/erlang/r13b04_hipe
r13b04 /Users/alind/Applications/erlang/r13b04

kerl activate r13b04 would call activate in the /Users/alind/Applications/erlang/r13b04 folder:

$ kerl activate r13b04
$ kerl active
The current active installation is:
/Users/alind/Applications/erlang/r13b04
@evax
Copy link
Owner

evax commented Jun 1, 2011

This would require spawning a new nested shell with an updated environment, and kerl makes no assumption on the shell being used.

@eproxus
Copy link
Author

eproxus commented Jun 1, 2011

I see, I was afraid of that. There's no other shell trickery that can be used to avoid that?

@evax
Copy link
Owner

evax commented Jun 1, 2011

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.
Would that suit you?

@eproxus
Copy link
Author

eproxus commented Jun 3, 2011

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.

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

2 participants