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

Improve message when executable cannot be found #1418

Open
kaste opened this Issue May 19, 2018 · 1 comment

Comments

2 participants
@kaste
Contributor

kaste commented May 19, 2018

Currently we output something like SublimeLinter: #2 linter.py:573: WARNING: lua cannot locate 'luac' if the executable cannot be found using a global which.

SublimeLinter: WARNING: (lua) Linter non-functional: Cannot find a binary 'luac' in PATH.

Maybe we should then print PATH as well. Or ask "Did you install 'luac' globally?"

As reported here SublimeLinter/SublimeLinter-lua#7

@braver

This comment has been minimized.

Show comment
Hide comment
@braver

braver May 19, 2018

Member

Ideally an error message contains a hint of how to solve it. So, if we’re sure globally installing something is the right solution we can suggest that.

Printing PATH feels like debugging to me. I would prefer something like “if this problem persists, please refer to our troubleshooting guide: (url) and the readme of this plugin”.

Perhaps we should do that anyway, so the plugin readme can tell you what the right approach to installation etc is.

Member

braver commented May 19, 2018

Ideally an error message contains a hint of how to solve it. So, if we’re sure globally installing something is the right solution we can suggest that.

Printing PATH feels like debugging to me. I would prefer something like “if this problem persists, please refer to our troubleshooting guide: (url) and the readme of this plugin”.

Perhaps we should do that anyway, so the plugin readme can tell you what the right approach to installation etc is.

@braver braver added the enhancement label May 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment