Closed esmevane closed 12 years ago
Strange behavior. Only the file extensions in the autosave configuration should trigger jslint. Could you specify your OS and list of user packages? To totally remove this package, you should be able to just remove JSLint from your user packages directory.
I'm not able to reproduce this. The lint-on-save feature changes the selected build system to JSLint when a .js, .css, .json or .html file. To revert the build system to Automatic, use the menu system to select Tools > Build System > Automatic. Unfortunately I haven't managed to programatically revert to the originally selected build system after doing lint-on-save, but pull requests are welcome.
Decided to not set the build system, but rely on the Automatic build selection and the file extension matching mechanism located in the build system specification itself. This means manually setting the build system ought to take precedence.
Commit f9e08ff21ba60799982a83fa056d8e6f1697add2
Darren, thanks for looking into this. Sorry I wasn't able to get you more diagnostic information sooner!
No problem, thanks for the tip.
Note: if you remove JSLint, under Tools / Build System, select the new build system you want Sublime Text 2 to use.
On Tue, Mar 5, 2013 at 11:45 AM, Anthony Bouch notifications@github.comwrote:
Hmm... I tried removing JSLint using the package manager, and now I'm getting this "Error trying to parse build system: No data in ~/Library/Application Support/Sublime Text 2/Packages/JSLint/JSLint.sublime-build:1:1" on all builds. How can I resolve this? ((Mac OS X).
— Reply to this email directly or view it on GitHubhttps://github.com/darrenderidder/Sublime-JSLint/issues/3#issuecomment-14450403 .
Thanks Darren - I realised that just after I posted here, hence the deleted post. But thanks for the quick reply anyway.
Best,
Tony
After installing this package, ALL of my build systems for ALL file types attempt to Lint. This is not on save, this is on Super + B and Super + Shift + B.
No amount of configuration changes seem to produce a change in this behavior, and uninstalling the package produces an even worse result - the build tasks are still all usurped, except that now JSLint has no build system to point to, and displays an error message.
I am still able to manually configure the build system for every individual file after I open it, but the configuration does not persist.