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:
Expected 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:
Summary
"Command not found" error when running
sltoo soon after opening a codespaceAfter opening a new codespace and running the
setup.shscript, running theslcommand too soon results in a "command not found" error. This happens because the environment variables are not yet fully set.How to reproduce
Expected Result
The
slcommand should run successfully.Actual Result
The terminal returns a "command not found" error.
Additional context
This issue occurs because the
slcommand 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: