<story><title>Google releases its own Javascript Lint tool </title><url>http://closuretools.blogspot.com/2010/08/introducing-closure-linter.html</url><text></text></story><parent_chain></parent_chain><comment><author>stevelosh</author><text>Here&apos;s a couple of lines to let you use this with :make (on a single file) and the QuickFix window in Vim:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    au BufNewFile,BufRead *.js set makeprg=gjslint\ %
    au BufNewFile,BufRead *.js set errorformat=%-P-----\ FILE\ \ :\ \ %f\ -----,Line\ %l\\,\ E:%n:\ %m,%-Q,%-GFound\ %s,%-GSome\ %s,%-Gfixjsstyle%s,%-Gscript\ can\ %s,%-G
&lt;/code&gt;&lt;/pre&gt;
If any experts in Vim&apos;s makeprg/errorformat want to clean this up, that would be awesome.  I just hacked it together and it seems to work well enough.</text></comment>
<story><title>Google releases its own Javascript Lint tool </title><url>http://closuretools.blogspot.com/2010/08/introducing-closure-linter.html</url><text></text></story><parent_chain></parent_chain><comment><author>maw</author><text>The installation instructions tell you to run &quot;easy_install &lt;a href=&quot;http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz&quot; rel=&quot;nofollow&quot;&gt;http://closure-linter.googlecode.com/files/closure_linter-la...&lt;/a&gt;.  All well and good, but install instructions that don&apos;t reference specific version numbers freak me out.  I might have gotten a little too much reproducibility religion, with all that that entails, but it seems better than being so cavalier when setting up environments.</text></comment>