-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Testing needed: new branch "preprocess" #753
Comments
@lcd047 I get the following error message on Windows with preprocess branch:
|
Ah, some code left over from testing, sorry about that! Please try 05dea5f. |
Strange, still the same message:
|
Please set :echo &shellpipe
:echo &shellredir
:echo &shellslash
:echo &shellxquote |
shellpipe and shellredir: |
Ok, I think I got it now, via some ugly plumbing. Please try 8f40f27. |
No, still no changes. |
Hmm. Looking at the sources, this seems to happen because |
No, still the same error. I tried prepending '&' to shellredir variable at line 362 of syntastic.vim (thought it might be a misprint, I don't know much about vim scripts though), to no avail. |
Sigh Ok, I give up, I have no idea how to make it work with Please try this version: ac87fd1. It uses plain |
For what it's worth, ghcmod-vim mentioned in #317 uses vimproc to achieve sane inter-process communication, and vimproc in turn delegates the problem to a dynamic library written in C. This is too restrictive for too little gain for syntastic. :( |
Yes, I can confirm that this branch now works on Windows and Linux. Tested with Haskell and C++ checkers. |
Ok, thanks. |
I take it there are no other problems left? ;) I'd like to merge this to master. If anybody sees any reason against it, now would be a good time to speak. |
I'm planning to merge this tomorrow morning. Last chance to complain. |
Done. |
Usin Windows gVim 7.4.27, on the main branch of syntastic I seem to be getting a similar error as slycelote, when using the python syntax checker.
|
@arecarn This may look the same, but it isn't related. Please upgrade syntastic to master HEAD, and if you still have problems post a new issue. If you do, please explain what you did, what you expected to happen, and what happened instead. |
I just committed a new branch named preprocess. This changes the way syntastic runs the checkers, essentially replacing
lmake
with the equivalentsystem
andlgetexpr
. As a result, error lines can now be preprocessed before being parsed, which can be used to bring some sanity to writingerrorformat
s, and elliminates the need for some of the external auxilliary scripts (see html/validator for an example). Shell quoting now works as expected (that part was a major pain withlmake
), and<NUL>
characters in checkers' output are now automatically translated to<NL>
s.Please test as many checkers as possible, and report any problems in this thread. Thanks in advance!
Edit: I'm particularly interested in hearing from people using Windows. Does this work at all?
The text was updated successfully, but these errors were encountered: