-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Racket checker runs GUI program #1773
Comments
Syntastic doesn't use, nor cares about, Vim's option Back to your problem: you can see the command lines constructed by syntastic in the debug logs (see You can change the command line constructed by syntastic by setting the various options (see |
Thank you very much for the explanation. Do you not think the checker should be changed if it actually executes the program under test? Would you be so kind as to point me to where the executed command is defined in the syntastic source code? |
Can @2sb18 Any comments on this?
|
This checker executes the code in the files it checks. This is probably fine if you wrote the files yourself, but it can be a problem if you're trying to check third party files. If you are 100% willing to let Vim run the code in your files, set g:enable_racket_racket_checker to 1 in your vimrc to enable this checker: vim let g:enable_racket_racket_checker = 1 There is also a buffer-local version of this variable, that takes precedence over it in the buffers where it is defined. Reference: #1773
Ok, assuming the worst. Commit 95879f1. |
Probably for the best. I will try out the alternative racket checker and try and define one based on |
This checker executes the code in the files it checks. This is probably fine if you wrote the files yourself, but it can be a problem if you're trying to check third party files. If you are 100% willing to let Vim run the code in your files, set g:enable_racket_racket_checker to 1 in your vimrc to enable this checker: vim let g:enable_racket_racket_checker = 1 There is also a buffer-local version of this variable, that takes precedence over it in the buffers where it is defined. Reference: vim-syntastic#1773
With vim-racket installed, working on a GUI program, the racket checker runs the GUI program,
:make
does not.vim-racket sets:
which might be a better option for the checker. I couldn't find where to define the actual checker as this line seems sort of magical.
The text was updated successfully, but these errors were encountered: