-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Error message isn't very informative: aura >>= Please check your input. #639
Comments
I know the spot in the code that is causing this to happen, and can fix this. In general it is caused by an error code floating up from one of the (many) pacman calls that Aura makes. In this case it's just making one for an |
One more case of hilariously inappropriate "Please check your input" message:
AlternativesAfter hearing "No", Pacman itself, however, exits with code 1 if denied to proceed: |
In these cases I'm going to match So I'll keep the exit codes, but silence the message. |
Thanks for reporting this, I'm glad to finally be rid of that spurious message. |
When your search (
-Ss
) does not yield any results,aura
prints this message and exists with status 1:When I first saw this error message, I thought I made a typo in flags or something. It most certainly tells nothing about the search itself —only my input. Input what? Like, have done something wrong? Do I have to read man aura's page all over again? Well, you get the idea: such error message is inappropriate and not actionable.
Interestingly enough, this does not happen when searching AUR (-As):
Expected behavior
Do nothing, say nothing, return 0. Or at least, say something meaningful.
Actual behavior
Prints [confusing] error message when nothing found in repositories (
-Ss
) for the given search terms.Alternatives
For example,
pacaur -Ss abcdefghi
prints nothing and exits with code 0.The text was updated successfully, but these errors were encountered: