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

[Bug] #138

Open
iriru opened this issue Jan 18, 2025 · 1 comment
Open

[Bug] #138

iriru opened this issue Jan 18, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@iriru
Copy link

iriru commented Jan 18, 2025

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

  1. Open a new codespace.
  2. Immediately run the sl command:
sl

Expected Result

The sl command should run successfully.

Actual Result

The terminal returns a "command not found" error.

Image

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
@iriru iriru added the bug Something isn't working label Jan 18, 2025
@iriru
Copy link
Author

iriru commented 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."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant