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

Multi-shell support #19

Closed
Schniz opened this issue Feb 3, 2019 · 1 comment
Closed

Multi-shell support #19

Schniz opened this issue Feb 3, 2019 · 1 comment

Comments

@Schniz
Copy link
Owner

Schniz commented Feb 3, 2019

I believe this can be a breaking change, therefore should mark a version 2?

In its core, the following thing should work:

bash 1            | bash 2       
------------------|-------------
$ fnm use 11.0.0  |
Using Node 11.0.0 |
                  | $ fnm use 10.0.0
                  | Using Node 10.0.0
$ node -v         | $ node -v
11.0.0            | 10.0.0

How would that work?

I guess we can create a directory in /tmp, that will contain symlinks. A symlink will be created every time we call fnm env! The system will clean it up itself, so there is no problem there:

$ fnm env
export PATH=/tmp/fnm_environments/terminal_xxyyzz:$PATH

This may relate also to #6, because we might have to implement some kind of "aliases". This shouldn't be hard as well because - it's also a symlink. Isn't that great? Everything is a symlink!

@Schniz
Copy link
Owner Author

Schniz commented Feb 11, 2019

This can also be opt in - fnm env --local

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

1 participant