-
Notifications
You must be signed in to change notification settings - Fork 737
[Bug] Using 'setup.sh' in step 4 doesn't work #98
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@czmoss Thank you for opening this issue, and submitting a PR with a fix! We will get this issue groomed ✨ |
Thanks for reporting this issue, @czmoss ❤. I updated the OP with acceptance criteria and a suggestion on how to resolve this. The path isn't being set in |
Thanks for the replies, @nguyenalex836 and @hectorsector! It's great to see that these courses are being actively maintained. As I indicated in the comment I just posted on my now-closed PR #99, my specific issue was that my dotfiles were not being installed, but that upon just redoing this course I am seeing that they are. I, personally, had no problems typing It is of course in your hands to determine whether the learning goals for this course are best addressed by expanding its scope slightly to include a discussion of environment variables and persisting them. I wish you luck! |
Hello, I have wrote a fix for these bug, I opened a pull request Link to 106 |
Summary
Using a file named 'setup.sh' in step 4 does not work to initiate installation of dotfiles (or, as this course has it, the
sl
steam locomotive).How to reproduce
sudo apt-get
lines, as instructed./usr/games/sl
Expected results and acceptance criteria
echo $PATH
should contain/usr/games
.export PATH=$PATH:/usr/games >> ~/.bashrc
todevcontainer.json
underpostCreateCommand
.sl
from the home directory should work.Additional context
I found that instead by using a file named 'install.sh', as documented in Personalize your codespaces#Dotfiles, during my "How to reproduce" step 4 (i.e., "Wait while the Codespace is set up.") I saw an "Installing Dotfiles" progress indicator in the terminal area.
The text was updated successfully, but these errors were encountered: