-
Notifications
You must be signed in to change notification settings - Fork 958
Environment not set up on Ubuntu at install #975
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
PATH handling needs overhaul completely. |
Hi, |
Specifically, we see the Ubuntu issue on Ubuntu 16.04.2 LTX (Xenial) using bash. |
EDIT: I misunderstood the issue that the users want to use Rust right after When we use export PATH="$HOME/.cargo/bin:$PATH"
exec "$SHELL" But there is unresolved question here:
|
I'm not sure what approach is best. Nominally |
Just looking through the code now, both |
Yes I just noticed that. In theory we should also support Do we think this could be closed? |
The problem I probably have, and I suspect many, is understanding the distinction between a shell and a login shell. Most people probably just want cargo to work immediately, or to launch a new terminal and have it work, but for most configurations they have to literally log out of their GUI to get .profile to run. I myself mostly work on WSL and I have no idea when .profile runs, but I've just discovered how to launch a terminal with a login shell (after years of frustration). The instructions do indicate how to get the current shell immediately working by sourcing @kinnison I kinda think this should be closed, but I'm still not happy with the install experience here. That it only works after a login is very confusing. I'm kinda thinking that putting some code in |
In fact, |
Okay, we'll continue the work from there and I'll close this, thank you @brson. |
(moved here from rust-lang/book#404)
@tsingi reported:
I think this is an issue with rustup and/or rustup docs, and I hope we can figure this out over here rather than having to document it in the book.
This might be related to #211, #556, or #371, but I'm not sure.
The text was updated successfully, but these errors were encountered: