Commit Graph

7 Commits

Author SHA1 Message Date
Martin Grenfell
892cc2c232 refactor the error highlighting system
* remove the public SyntasticHighlightErrors() function
* shift the above code into s:HighlightErrors(). This is called
  automatically if g:syntastic_enable_highlighting is set
* to get the highlight regex we just look for a function called
  Syntastic_<filetype>_GetHighlightRegex
* to force this function to be called, each error item must have the
  'force_highlight_callback' key set

This code has one important functional change: now errors are *always*
highlighted if possible whereas previously they were only highlighted if
a call to SyntasticHighlightErrors was made.
2012-03-02 10:05:15 +00:00
Gilles Ruppert
be1091f251 rather than compare to '' we use the vimscript emtpy function as else the check does not work 2012-02-11 21:45:30 +01:00
Gilles Ruppert
c2c0058973 make the ternary check for the javascript jshint config explicit as else it was not working on my system 2012-02-11 02:27:45 +01:00
Martin Grenfell
c05a36f66c jslint: update for jslint 0.1.4 2012-01-06 19:06:47 +00:00
Martin Grenfell
58cd0d340c update the javascript/jslint syntax checker
The jslint guys have changed their error format again. Update the syntax
checker to handle it.

Currently jslint outputs a "use strict" error if a function doesnt have
'use strict' at the top. This is not good for our purposes, so just
filter this out for now.
2011-12-23 23:09:03 +00:00
millermedeiros
e4adda29f7 fix jshint checker since it was ignoring jshintrc configs. 2011-12-16 16:28:24 -02:00
Martin Grenfell
394d129b55 refactor the javascript syntax checkers
The js syntax checker was 4 checkers stuffed into 1 file. Now it is
broken down so that each checker is in its own file inside
syntax_checkers/javascript/ while syntax_checkers/javascript.vim just
determines which file to source.

Change the names of the global js checker config variables so that
they all start with "syntastic_javascript_". This is purely for
namespacing.

Remove some unneeded logic around the config variables too. Not sure how
it got in there, but it was more confusing than helpful without offering
any benefits...
2011-12-11 22:54:33 +00:00