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

Request: When no appropriate token is present, shell-fm -d should exit with non-zero status, and send the token url to std_err. #81

Open
AndydeCleyre opened this issue Feb 22, 2013 · 0 comments

Comments

@AndydeCleyre
Copy link

As it is, with no token or an expired token, launching shell-fm normally (not as a daemon) exits immediately with error status and an error message:

This token has not been authorized.
Failed to create session. Please refresh authorization.
Please open http://www.last.fm/api/auth/?token=[ . . . ] in your browser to authorize shell-fm.

In contrast, launching shell-fm with the -d flag under the same circumstances appears from the outside to be a silent success, but in reality exits immediately as well, only with no error status, no error message, and no url.

I request that running shell-fm -d without an appropriate token result in a non-zero exit status, and the token url output to std_err.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant