Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vim installation not working #781

Closed
matthewepler opened this issue Feb 9, 2017 · 3 comments

Comments

@matthewepler
Copy link

commented Feb 9, 2017

Syntastic has been installed and is confirmed to be working by running :SyntasticInfo from inside Vim. That produces this:

Syntastic version: 3.6.0
Info for filetype: javascript
Global mode: active
Filetype javascript is active
The current file will be checked automatically
Available checkers: -
Currently enabled checkers: -
Press ENTER or type command to continue

Inside my .vimrc file, I have the following:

let g:syntastic_javascript_checkers=['standard']

And when I run a standard command, standard ./test.js, I get good output:

standard: Use JavaScript Standard Style (http://standardjs.com)
  /Users/matthewepler/test.js:2:24: Parsing error: Unterminated string constant

So if all the individual parts are working, why isn't standard showing up as the checker for Syntastic?

Forgive me if this is a Syntastic error, but because it seems to give good output with the :SyntasticInfo I assume the error is elsewhere.

@feross

This comment has been minimized.

Copy link
Member

commented Feb 9, 2017

Maybe Syntastic can't show errors if there is a serious error like a parse error? Can you try a simple error like a semicolon:

console.log('hi');

📢 Any Syntastic users able to lend a hand here?

@feross feross added the question label Feb 9, 2017

@matthewepler

This comment has been minimized.

Copy link
Author

commented Feb 9, 2017

Cleared my .vimrc of a bunch of garbage and all was fine. My bad. will close immediately and proceed to shame myself.

@feross

This comment has been minimized.

Copy link
Member

commented Feb 9, 2017

@matthewepler Glad you got it figured out. No shame needed. 😅

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.