herr kaste
herr kaste
Yeah sure, but SublimeLinter gets a new issue like every hour.
(Disclaimer: I'm not an official reviewer here.) - `word_wrap` can have 3 states: true, false, and "auto". Typically (by default) it should be "auto" which is "trueish" and therefore your...
Lastly: I would probably make the core functionality a `TextCommand` (which we can bind to a key or so) so that if we disbale `on_hover` we could still trigger it....
I had several problems with the current Sublime build and its 'build' functionality. See https://github.com/SublimeTextIssues/Core/issues/2293#issuecomment-391638957 I also have a patch right there. Maybe https://github.com/SublimeTextIssues/Core/issues/2327 is relevant too.
Each error can have exactly one style in SublimeLinter, a different style for the line and the word TODO is not possible. Since these lines would contain whitespace only outline...
Short term, you could just implement find_errors and yield LintMatch'es t.i. it should not be necessary to implement run. run actually is the entrypoint to the popen thing and ideally...
The original feature request could also be an add-on. You just listen for on_lint_result and whenever you find an error you're interested in, e.g. when it's an annotations error, you...
It should just work. What have you tried? What are you missing? Have you `npm install -g jshint`?
There is always a way. We probably need to run `flow start` once per `flow-bin`. However, we never call `stop` 🤔 ?