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

consistent use of @env vs env #930

Closed
StefanKarpinski opened this issue Nov 27, 2018 · 4 comments · Fixed by #1488
Closed

consistent use of @env vs env #930

StefanKarpinski opened this issue Nov 27, 2018 · 4 comments · Fixed by #1488

Comments

@StefanKarpinski
Copy link
Member

I'd like to propose consistently using @env as syntax for a named environment with name env. This would allow doing something like pkg> activate @devtools to activate ~/.julia/environments/devtools no matter where you are. The main issue would seem to be conflicting with the @1.1 version syntax, but I'm not sure that's an actual ambiguity anywhere. Thoughts?

@fredrikekre
Copy link
Member

And remove --shared?

@StefanKarpinski
Copy link
Member Author

This does seem like it would be more intuitive, doesn't it? I always forget about shared and I want to just call named environments @env everywhere.

@KristofferC
Copy link
Member

Seems like a simplification. @name if you just want to identify it by name. path/name if you want to identify by path.

@StefanKarpinski
Copy link
Member Author

Note that as part of this we should use @env consistently to display shared environments as well. So the prompt should be (@v1.1) pkg> instead of the current (v1.1) pkg>. The idea is that if you do pkg> activate @v1.1 then the prompt you get afterwards is (@v1.1) pkg>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants