herr kaste

Okay, cool. Before I do the code review... The normal executable finding is done via ``` for path in paths_upwards(path): node_modules_bin = os.path.join(path, 'node_modules', '.bin') executable = shutil.which(npm_name, path=node_modules_bin) ```...

Even using pen and paper I did not find a good implementation yet. Keep in mind that I need to resolve all open issues at once if I do or...

Sure, I tried to move it but I admit I never felt I fully grasp it.

Glad you're back! - The manual 'executable' workaround should be applied 'locally', LOL?, t.i. not in the 'SublimeLinter.sublime-settings' but in a '*.sublime-project' file. So you apply the workaround only for...

There is some progress here. I've made an initial PR https://github.com/SublimeLinter/SublimeLinter/pull/1579 against SL core. If that lands, I think we can make a simple change here to support that use-case...

Basically, at the same time we discussed here, eslint started its breaking versions overhaul. Global installs are seriously discouraged, globally installed plugins even more, usage of a personal config file...

@braver for critique. I only implemented `fix_on_save`. Should we also have `fix_on_manual`? (A bit stupid: 'manual' also triggers for config changes. (That's actually the reason I did not include it...

Hm, the regions move around. Slow motion gif:  🤔

Okay. If we use on_pre_save we can generally modify the buffer and Sublime will save afterwards. But we need to be sync then which is bad. on_post_save, we generally get...

But the moving regions are awesome. 👯‍♂️