Very frequently, I have both the syntax definition and a test file open side-by-side, but the linter does not re-lint the file when the syntax is changed, requiring me to switch focus and either make an edit or save the test file first before the lint results are refreshed.
It would be a huge QoL improvement if the plugin could trigger a re-lint from SL by itself when a syntax definition was updated (i.e. saved from within ST).
Listening to an on_save_async event is trivial, but I'm unsure what the best approach to trigger a re-lint is. I have found out that a sublime_linter_lint TextCommand exists, so I could trigger that for each view I deem to be a syntax test file, but I imagine that this functionality would be useful for other linters as well when their respective configuration files are edited, so perhaps we can coordinate something with the SL core here.
Very frequently, I have both the syntax definition and a test file open side-by-side, but the linter does not re-lint the file when the syntax is changed, requiring me to switch focus and either make an edit or save the test file first before the lint results are refreshed.
It would be a huge QoL improvement if the plugin could trigger a re-lint from SL by itself when a syntax definition was updated (i.e. saved from within ST).
Listening to an
on_save_asyncevent is trivial, but I'm unsure what the best approach to trigger a re-lint is. I have found out that asublime_linter_lintTextCommand exists, so I could trigger that for each view I deem to be a syntax test file, but I imagine that this functionality would be useful for other linters as well when their respective configuration files are edited, so perhaps we can coordinate something with the SL core here.