4.28.2

• Fix a long-standing bug where fast "modify, save" successions would lead in linting being skipped. Wrongly de-duped one could say. (That was part of #1985.)

4.28.0

SublimeLinter always had lint modes like "background" or "load_save" which
describe on which circumstances a linter may run but are relatively
coarse-grained. We now allow a list here with the modes "on_save", "on_load",
"on_modified" which can be combined as the user wishes.
Refer https://www.sublimelinter.com/en/master/linter_settings.html#lint-mode
for more details.

The command sublime_linter_lint learned a new arg run which specifies
which linter(s) you want to run. Previously, always all valid linters for a
view did run. This new arg is also used as an optimization when reloading the
config or a linter class.
We also expose the related function hit to trigger linter runs programmatically.

Announcing https://github.com/kaste/SublimeLinter-any-lsp which is an adapter
for any LSP server.

Sincerely,
💕

Yes, I do enjoy coffee: https://paypal.me/herrkaste

4.27.1

• Revert humanizing the column shown in the panel as it was in conflict with Sublime's next_result/result_line_regex implementation.

4.27.0

• Rename ComposerLinter -> PhpLinter.

• PhpLinter learned disable_if_not_dependency

• For PythonLinter, VIRTUAL_ENV is set and PATH expanded automatically if
  a virtual environment is found. (mypy uses this right now.)

• Noticeable: the error panel will show the visual column when you're using tabs.
  (Just like Sublime's status bar.) Reverted in 4.27.1

• Maintenance as always.

4.26.0

BREAKING CHANGE: TL;DR - By default, only whole files are linted from now on.

SublimeLinter was always capable of linting just parts of a view if the whole
file did not match a given "selector". E.g. it could lint code blocks inside
markdown documents. There was no way to opt-out of this behavior, except
maybe to use the excludes setting to exclude all *.md files, although most
linters don't have a good understanding of such sub-blocks -- let's call them
cells, as in: notebook cells.

v4.26.0 introduces a new setting enable_cells which defaults to False
(which makes it a breaking change). Plugin authors can opt-in in their
plugin, so can users, on a case-by-case basis.

E.g. you could still let flake8 run on python blocks in your docs if
you want to but then probably also configure per-file overrides, e.g. to only
report whitespace errors or to exclude any unused-var warnings, etc for them.

Sincerely,
💕

Yes, I do enjoy coffee: https://paypal.me/herrkaste

4.25.1

• Fixed long standing bug in the status bar view. (#1948)

4.25.0

--- @WZ-Tong implemented the setting show_panel_on_save.ignored_error_types to suppress the automatic panel popup for certain error types.

You could set it to ["info", "hint"] for example.

That's it, sincerely,
💕

4.24.3

• Redo the hot-fix applied to 4.24.2
• Never choose the user's HOME directory as the project root only because it has some configuration files in it.
• Fix edge-case in the squiggles code. Apparently sometimes Sublime can't compute a foreground color for a given scope; just fallback in those cases.

4.24.2

Reloading always threw a RuntimeError. That doesn't have to be so. (#1937)

4.24.1

The current stable version of Sublime Text, build 4169, has a bug requiring a
restart after a fresh and clean install of SublimeLinter.
This release just adds an installation note about that.