herr kaste

Well that looks like rubocop can lint haml files directly because that's what you do on the command line. Interestingly we explicitly exclude haml portions here in the plugin. Look...

I reread your initial post. On the command line you tell it to lint the haml file but it reports 0 files inspected. So it basically ignores the file. Probably...

Yeah sure, but it looks like it actually ignores the file. For that, you could set "exclude" to maybe "*.haml" in the settings. The question is if we can somehow...

The default selector explicitly extracts parts of the haml file, the Ruby parts, and sends them separately to rubocop. It does not send the whole file. I don't know if...

Well, generally the `selector` we ship should already *exclude* haml files as it is `source.ruby - text.html - text.haml`. That is with the default Ruby HAML syntax shipping with Sublime...

We rejected to add external sources by default recently bc we're not sure if it is good default. Is it supported everywhere? Since when? Why is it a flag if...

That's a known limitation. The `"env"` mapping is used for the linter (child-) process not to enhance the (parent) lookup process (which would be the shared python plugin host process...

Conecptually it's part of https://github.com/SublimeLinter/SublimeLinter/issues/1795 Using `env/PATH` is the first step to implement 1795.

You mean the short log/graph in the status header. (Do you have a pic otherwise?) In the graph it's `o` (for _o_pen). (Or `m` for the split view with a...

Yes, support for worktrees is on the wishlist. It is important to have new commands which integrate into what we already have For example, - you look at a "random"...