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.
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.
The goto command is configurable. Check the keybindings file for the options.
We don't support sublimelinterrc files anymore.
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.