Macvim jslint issue? about syntastic HOT 3 CLOSED

I was experiencing the same problem with jslint that I installed from MacPorts. Some syntastic debugging showed that the errorformat was not matching anything into the loclist:

        let errorformat='%-P%f,%*[ ]%n %l\,%c: %m,%-G%.%#'

You should test two things:

• Start a /bin/bash and make sure that shell has jslint in its path by running which jslint. If it doesn't, you should fix that as you might be running into this default shell replacement hack:

    if !s:running_windows && (s:uname !~ "FreeBSD")
        "this is a hack to stop the screen needing to be ':redraw'n when
        "when :lmake is run. Otherwise the screen flickers annoyingly
        let &shellpipe='&>'
        let &shell = '/bin/bash'
    endif

• Run jslint on one of your source files and make sure that one of the first lines is the filename you ran jslint on.
  If the name of the checked file does not appear in the jslint output, you are probably not using node-jslint. You have two options:
  1. Get the proper jslint from npm by running npm install jslint [-g], or cloning https://github.com/reid/node-jslint
  2. Edit your errorformat in the syntastic bundle to suit yout jslint's needs.

from syntastic.

I wouldnt be at all surprised if the jslint and jshint output has changed since the checkers were written. I have been using the gjslint checker - which seems to work fine.

If you really want to use jslint or jshint then it will almost certainly be necessary to update the errorformats for them.

I am considering dropping one or 2 of the javascript checkers since it is just more work to maintain and I only use one. Either that or spam the original authors of those checkers.

from syntastic.

I have fixed jshint/jslint.

The error formats are based on jslint 0.1.0 and jshint 0.5.3.

Check these 2 commits for details:

8ca2028
70166f4

Comment here if there are any problems :)

from syntastic.