Commit Graph

56 Commits

Author SHA1 Message Date
Buck Golemon
c039b0f128 fix pylint parsing 2012-03-11 22:04:47 -07:00
Parantapa Bhattacharya
760d84588e Fix pylint error format string
Used the error format string from sashahart/pylint.vim which seems
to be much more comprehensive.
2012-03-04 13:03:09 +05:30
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
Martin Grenfell
637182c181 python/pyflakes: report errors by default
The error messages that pyflakes outputs dont contain enough information
to classify them as errors or warnings. Apart from checking for all
known warning outputs and classifying the rest as errors (or vice versa)
there is no way classify.

Make the syntax checker class all results as errors. Individual warning
formats can be checked for later if they become a problem.

This addresses #189.
2012-02-28 15:19:32 +00:00
Martin Grenfell
bcfdab6a02 python: bugfix to pyflakes checker
dont refer to g:syntastic_python_checker since - due to a previous
commit - this is not guaranteed to exist any more.

This change should have been done in the aforementioned commit - but I
failed.
2012-02-23 13:24:34 +00:00
Martin Grenfell
d454a00615 split python checker out into 3 files
previously there were 3 checkers in the one file
2012-02-20 10:20:48 +00:00