Repository navigation
[Bug] #138
Description
Summary
"Command not found" error when running sl too soon after opening a codespace
After opening a new codespace and running the setup.sh script, running the sl command too soon results in a "command not found" error. This happens because the environment variables are not yet fully set.
How to reproduce
- Open a new codespace.
- Immediately run the sl command:
slExpected Result
The sl command should run successfully.
Actual Result
The terminal returns a "command not found" error.
Additional context
This issue occurs because the sl command is run before the environment variables are fully applied. To prevent this, please wait a sufficient amount of time before running the command. If the issue has already occurred, try the following method:
source ~/.bashrc
sl
Activity
iriru commentedon Jan 18, 2025
"Issue might be caused by user error, but I wanted to document it as I continue to learn. I will also try to create a pull request for this issue later, but unfortunately, I can't do more at the moment."
docs : Update 4-personalize-codespace.md
iriru commentedon Jan 19, 2025
@jhonatanparada499
, there are currently no reviewers available for this pull request. Could you please review it and merge if everything looks good? Thank you!
nguyenalex836 commentedon Jan 20, 2025
@iriru Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛
tfredrick112 commentedon Apr 25, 2025
@nguyenalex836 I found that updating the postCreateCommand helps solve the issue, can you please review this PR and merge if it looks good? #160
v-fidelusaleksander commentedon Jan 28, 2026
The exercise just got a major update and this should be fixed
jhonatanparada499 commentedon Jan 28, 2026
@iriru
Why are you calling me?