herr kaste

The focus stuff is just in here. https://github.com/SublimeLinter/SublimeLinter/blob/e0fee64ce4a50a57edc67056f688598f4cef94b0/panel_view.py#L291-L296 Basically, the first focus line on L292. Before we always moved focus back to the view here which is now in a...

So generally `window.open_file` now steals the focus. I added a commit to bring the focus back to the panel. More generally, ST4 is laggy. It is slower for this operation,...

The focus management is a bit special in ST3 because output panels behave special here. For example if a panel has focus, you cannot just `focus_view` a normal view, you...

Let's call it what it is. You use alpha software here. 1. `window.open_file` activates the view *iff* the file is the same as the already `active_view` (t.i. a "real"/"normal" view)...

Okay, the innocuous looking `panel.find_all_results()` I use here (because it was there and did what I needed) has a performance excess even for rather few items in the panel (or...

Well, no, I just used `find_all_results` because it was there. We just use our error store. I mean sure we know which error we just draw in the panel.

Well, the combination of mouse interaction and keyboard navigation is not well defined. I basically focused on the keyboard driven workflow because it is the initial workflow this PR wants...

> Huh. I did truly "go prev" on top a file just now: The native "prev_result" goes to the previous file, but the "prev_commit" (arrow ⬆️) I implemented here doesn't....

That's a difficult one. I actually wouldn't want to make significant UX changes without some form of community behind it. Generally, this kind of exploit is possible in eg vim/ALE...

Windows Defender will detect malicious software on `git clone` or when we execute it. I really don't think it will not.