Sublime Forum

**braver** · February 18, 2018, 8:30pm

I was afraid you’re going to say that. This is not the right place for that question, I think you could try stack overflow. Also, most linters are open source, so you can start from one of those. You’re not going to find a 101 that will help you get one going without a serious time investment if you don’t already know where to start.

**michaelblyons** · February 19, 2018, 5:21pm

Two things:

Can you update the link in the first post for “all the details here” to master from next (now that next is gone)?
The change from .sublimelinterrc to *.sublime-project is really great!! But I can’t find any documentation for it.

I finally found a bug report where someone had posted their Project file with its SublimeLinter section, and I was able to work out what to do. It’s really simple when you see an example, but nigh impossible without knowing the format. Is there a place where the new override syntax is documented?

**braver** · February 19, 2018, 6:29pm

When sl4 is released the docs at SublimeLinter.com will be updated, but you can always read the current docs in the docs folder of the repo: https://github.com/SublimeLinter/SublimeLinter/blob/master/docs/settings.rst

**braver** · February 28, 2018, 9:47pm

Just as a heads-up: SublimeLinter 4 is imminent. Possibly this Friday. If you’re scared, opt out asap, otherwise: LINTER IS COMING!

**braver** · March 2, 2018, 11:29am

Alright, we’re live, 4.0 is out there right now. If you’re having problems, check the issues for the current status and possible work arounds. Mostly restarting Sublime Text helps a lot, so do that at least twice

**rchl** · March 2, 2018, 12:39pm

I feel like something is wrong with the font used in the tooltip.

**rchl** · March 2, 2018, 12:43pm

I’ve figured that one out. I had font_face setting set to font that I didn’t have on my system (Hack). While the editor itself has fallen back to a default, seems like tooltips don’t have the same fallback logic. Solution was to remove that setting.

**devcarlos** · March 4, 2018, 11:26am

How do I disable this in the status bar as I like to keep my status bar minimal.

**braver** · March 4, 2018, 8:17pm

Hey, I don’t think we have a setting for that actually. I’ll look into adding that.

**devcarlos** · March 4, 2018, 9:43pm

Thank you

**braver** · March 6, 2018, 7:45am

Just pushed out 4.0.3, should land any minute now with options to completely tweak how and if we show stuff in the status bar!

**devcarlos** · March 6, 2018, 11:11am

Works like a charm thank you.

**goodrankuser** · March 6, 2018, 11:36am

guys how i can actived my ignore warning list?

       "htmltidy": {
            "@disable": false, 
            "args": [], 
            "excludes": [], 
            "ignore_match": [
                "missing <!DOCTYPE> declaration", 
                "inserting implicit <body>", 
                "inserting missing 'title' element", 
                "trimming empty <span>"
            ]
        }

and i try add my tidyConfig.txt in arg but nothing =
"args": ["-f tidyErrors.txt -config tidyConfig.txt"],

**braver** · March 6, 2018, 11:53am

Could you open an issue in the repo? That makes it easier to get more eyes on it.

**braver** · March 6, 2018, 6:56pm

There have been some requests to provide more background on some of the user-facing changes. So here:

No “(SL)” color scheme files are generated, in stead relying on common scopes.

Why it had to change:

We wanted to introduce flexible, per-linter and even per-error-code colors, a much requested (and awesome honestly) feature.

Why what we had was bad:

The user settings isn’t actually the only place you can set a color scheme.
It was super tricky for color schemes to prevent the modifications.
It wouldn’t respect the color scheme’s colors.
It was pretty much impossible to work on color schemes with SL3 installed.
Generating color schemes and then editing the user settings means we had to intrude the user space. For instance, writing to the user settings would wipe all comments from it.
The way color schemes were modified breaks in new ST builds.
New ST builds introduce new features to extend color schemes that are very easy to do by hand.
New ST builds generate “colorish” scopes for us.
Most color schemes implement the scopes we use now.

So, we had to option to put effort into maintaining what was a really bad idea, with new ST build already making that effort a waste. Or make it work for 99% of cases without any effort.

The context menu is for stuff relevant to the context, so it now only lists the Lint This View command.

The tools menu has been removed.

We had a lot of ways to change settings. How our settings work had to be completely redone. A lot of how we dealt with settings was counter-intuitive and worked completely different from other packages. E.g. it didn’t use standard mechanisms to merge the settings, and it used commands to interact with them (which would remove comments from them, really annoying). We were making really big changes here and would basically have to recreate all 5 different ways to modify settings that SL3 had. Or not, and spend that time testing, improving performance and adding other features.

We’re looking at new ways to toggle linters. Because we use normal settings mechanisms we have a chance of doing it right this time.

The settings “ignore_matches” and “demote_to_warning_matches” have been removed. As has support for .sublimelinterrc files or inline settings.

It makes no sense to have something be a warning in SublimeText (or be hidden), but an error on the command line. In the years since most of SL3 was designed most linters have become more mature and now have configuration files, and/or take arguments.

“make_warnings_passive” and “show_errors_on_save” are gone

We have a new output panel feature that should be an improvement for most use cases. We’re looking into restoring something like the show_errors_on_save feature now that we have a better picture of the problem it solves.

Other settings that are gone

error_color, warning_color

There is no way to implement thes setting without generating color schemes.

gutter_theme_excludes

The feature that used this is gone.

tooltip_fontsize, tooltip_theme, tooltip_theme_excludes, tooltips

In stead of multiple tooltip themes that are all terrible and settings you don’t need, we now have one good theme.

wrap_find

The goto command is configurable. Check the keybindings file for the options.

rc_search_limit

We don’t support sublimelinterrc files anymore.

use_current_shell_path

We don’t mess with paths so much anymore, which solves a lot of problems for a lot of users, but may require some work arounds on a Mac. It’s not a 100% win, but the outcome is still very positive.

**goodrankuser** · March 7, 2018, 8:12am

**mauroreisvieira** · April 24, 2018, 8:38am

Hi @braver

Why you remove the option “statusbar.counters_template”?
This options is very useful, to understand better the warning and errors in code…

You can create a identification in files in sidebar to user undestand how files have changes and errors? More or less like vscode.

p.s: Great work!

**braver** · April 24, 2018, 9:10am

Why you remove the option “statusbar.counters_template”?

We have more fully featured, and more complicated, feedback for each linter, and that didn’t match too well with the templating. I’ll think about bringing it back though.

You can create a identification in files in sidebar to user undestand how files have changes and errors?

There is no api to affect the sidebar in any way. So, we can’t change the icons or colors to indicate a file’s status like you would in VS Code or Atom.

**mauroreisvieira** · April 24, 2018, 9:59am

@braver, thanks for you answer.
I can configure the linter options to show the error like previous?

e.g:

“statusbar.counters_template”: “ {warning} {error}”,

**braver** · April 25, 2018, 6:55pm

It’s a bit different, but the template is back!

SublimeLinter 4 beta