Closed janraasch closed 11 years ago
Awesome. Thanks!
so how do I augment the .sublime-build file without getting it overwritten by each plugin-update? Where am I supposed to do it? Putting a custom JSLint.sublime-build to /Packages/User folder doesn't do the trick.
UPD: I've found out it's done in .sublime-settings file (by looking into the .sublime-settings file here on github). I don't have that in my local .sublime-settings file though, my standard installed one contains only this:
{
"filename_filter": "(\\.js|\\.css|\\.html|\\.json|\\.sass|\\.less)$"
}
Seems like the PackageControl doesn't load the new version of the plugin. Any idea why?
UPD 2: ok, it's actually effective only in @janraasch tree.. why is this still not in the master branch?
There was a problem with Windows and node-jslint
.
I really like your plugin, but the problem about using a
.sublime-build
is that though a user can edit the build settings in thePackages/JSLint/JSLint.sublime-build
file, but those changes maybe overwritten any time the plugin is updated.So:
js_lint_exec
, which basically runs a custom build reading the settings merged from the defaultPackages/JSLint/JSLint.sublime-settings
and customPackages/JSLint/JSLint.sublime-settings
I do realize that this is basically a whole new plugin (codewise at least), but I don't want to add another sublimetext-jslint plugin to the package control repo, since there are already two of them. So, if you'd like to pull this stuff into your repo, please go ahead.