lint_mode "save only" missing

[adamcobabe]

Not sure why "save only" lint_mode is missing in the new version. Please bring it back.

[FichteFoll]

It's right there:

SublimeLinter/SublimeLinter.sublime-settings

Lines 38 to 42 in fda38b6

	// Lint Modes determine when the linter is run
	// background: asynchronously on every change
	// load_save: when a file is opened and every time it's saved
	// manual: only when calling the Lint This View command
	"lint_mode": "background",

[gvuyk]

"load_save" != "save_only"
It was nice for reading other people's code

[braver]

Why not use “manual” for that?

[adamcobabe]

Because it's nice to be able to view other's code and not see thousands of lint issues AND not have to remember to manually lint on my own code--two birds, one stone. Good for refactoring.

[braver]

Well I can see that. Shouldn’t be hard to implement either.

[kaste]

I would like to see a change here for background mode as well and change the behavior of the BackendController.

We can have three modes (background|save|manual) plus a flag lint_on_load(true|false). Basically I could set background and lint_on_load to false for navigating through a code base, and linting would begin when I begin to write code.

Also to change: we hit on save in background mode which is not necessary.

	on_activated => skip if lint_on_load == false or lint_mode == manual
    on_save => skip if lint_mode != save
    on_modified => skip if lint_mode != background

This becomes a bit more complicated for

• when saving a project file fire config_changed event
• on_activate check if the syntax changed. For convenience we hit here bc there is a good chance that the assigned linters changed as well

Notable: if the config changes, we currently hit every view regardless of the lint_mode