-
Notifications
You must be signed in to change notification settings - Fork 24
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
:make Error "Usage|| see --help." #37
Comments
Could you send a screenshot and your Vim version? ( |
|
yes, it happens with any erlang file which has syntax error. even after correcting the errors, the |
i am using following vim plugins
|
Thanks for the plugin list. Could you disable Syntasic? It is known to cause issues for vim-erlang-compiler: #35 |
i moved syntastic out of and tried to recreate the error, but i am getting same behaviour. i.e. if i reload the file, |
Could you sent a screenshot? |
Could you type this when :make doesn't work and send the output?
makeprg is supposed to look like this:
:make should replace % with the file name and pass it to erlang_check.erl. But it seems that nothing is passed to erlang_check, not even --outdir, because erlang_check prints "Usage: see --help." only when it gets no parameters at all. |
when
if reload the file, and
i checked |
I added a few debug printouts that will help to narrow down the problem. Could you do the following:
When you save an Erlang file and the errors are automatically shown, When I save an Erlang file, I see this in
This means that GetLocalInfo saves the options, AutoRun modified them, and then SetLocalInfo resets the original value. |
i get the following output
|
i think i narrowed down the issue to one plugin.
if i remove this plugin,
not sure how this plugin resets the |
whenever there is a syntax error in the erlang file, and upon saving the file, the error window appears, the
:make
command always fails with above error after fixing the error.i have to quit and reopen the erlang file to make
:make
work.The text was updated successfully, but these errors were encountered: