I can’t remember where I found this, but I am using a script that runs the current file through JavaScript Lint (http:// www.javascriptlint.com/) rather than JSLint and displays a Project Search-style window of all the errors.
1. Install Javascript Lint (`brew install jsl`, if you have Homebrew installed) 2. Grab the script from here https://gist.github.com/1216037 3. Ensure that the path is correct (mine was `/usr/local/bin/jsl` by default) 4. Install the script Hope this helps. Samuel. On Sep 13, 11:02 pm, Daniel <[email protected]> wrote: > So I've been working to integrate JSLint more tightly into my coding > workflow. Obviously, running it from the web interface is a pain but > luckily I got it running on the command line thanks to Echo Ditto Labs > (http://echodittolabs.org/blog/2011/01/running-jslint-command-line). > > The process I have now is that I copy the file path from the BBEdit UI > (File Path > Copy Path), then I open terminal and type "cat /path/to/ > file | jslint" > > That's not bad, but I would absolutely love it if any of you know any > ways to integrate that more tightly into my coding process, so that I > could regularly run it through JSLint while I'm coding. Is there a way > through the BBEdit interface to just say "run this file through the > shell script and give me the output"? > > Any help is much appreciated! > > -Daniel Christopher -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
