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

CheckSyntax doesn't check anything #30

Open
peci1 opened this issue Jan 14, 2016 · 3 comments
Open

CheckSyntax doesn't check anything #30

peci1 opened this issue Jan 14, 2016 · 3 comments

Comments

@peci1
Copy link

peci1 commented Jan 14, 2016

I just installed CheckSyntax via pathogen (placed in ~/.vim/bundle/checksyntax). When pressing <F5> or manually calling :CheckSyntax, everything seems to run as it should, except no errors are reported (calling :ll and :cc returns empty lists). Tried with Java (jlint installed) and bash (bash -n correctly reports the errors when run from commandline).

I run Vim 7.4 on Ubuntu 14.04 64bit.

This is a relevant part of my vimrc:

let g:checksyntax#auto_enable_rx='.'
let g:checksyntax_auto=2

execute pathogen#infect()
@tomtom
Copy link
Owner

tomtom commented Jan 14, 2016

I'm sorry but checksyntax is currently unmaintained. It probably wouldn't be too difficult to fix things but I currently don't have the time for maintaining plugins I don't use myself on a daily basis. And since I use vim only for writing nowadays ...

@tomtom
Copy link
Owner

tomtom commented Apr 12, 2016

You could try

set verbosefile=/home/tom/vim.log
15verb CheckSyntax

and then post the relevant lines from vim.log. Most of the time, either the errorformat expression is wrong for your configuration, or checksyntax cannot find the executable.

@tomtom
Copy link
Owner

tomtom commented Mar 9, 2017

Well, I assume this issue isn't relevant anymore. If it is, you could try two new ways to get hold of the problem:

  1. Use let g:checksyntax#debug = 2 which gives you some additional hints.
  2. Install tlib_vim and then type :Tlibtraceset --file=checksyntax.log +checksyntax to get a more detailed trace. Send me checksyntax.log.

If the issue isn't relevant any longer (i.e. if you don't answer), I'll close it in a few weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants