aws / aws/amazon-q-developer-cli
Path does not contain ~/.local/bin
- Vorherrschende Sprache
- Rust
- Sterne
- 2k
- Forks
- 439
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
### Operating system
macOS 15.5.0 (24F74)
### Expected behaviour
# Overview
`q doctor` outputs the following error message after installing the Q CLI:
```
✘ PATH contains ~/.local/bin: Path does not contain ~/.local/bin
✘ Doctor found errors. Please fix them and try again.
If you are not sure how to fix it, please open an issue with q issue to let us know!
```
## Workaround
The path can be modified manually in zsh with this command:
```
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc; source ~/.zshrc
```
Followed by restarting the shell manually or with this command:
```
exec zsh -l
```
### Actual behaviour
Q Doctor reports that the required path value is not found. However, it doesn't help the user resolve this issue in any of the following ways:
- Update the path itself automatically
- Point to relevant documentation that explains how to update the path
- Telling the user what commands they could use to address the problem
I'm not sure what the preferable approach is given the tool's scope, but one or more of these would likely be an improved user experience.
### Steps to reproduce
Running `q doctor` without setting the required PATH variable first (and restarting the terminal).
Beitragsleitfaden
Rechercherichtung
Start by running `q doctor` without ~/.local/bin in PATH and review how it reports the PATH check. Compare the reported failure with the workaround using ~/.zshrc and `exec zsh -l`. Done means the doctor output gives users a clear, actionable way to resolve the missing path, whether through commands or relevant documentation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust, zsh
- Bereich
- cli, developer-experience
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100