The patch from Ozaki (posted at
https://groups.google.com/d/msg/vim_dev/LhXQJusQScM/_wV4u5y5AAAJ, in
https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cca137) fixes this
(only looked at the test suite for Neomake without the "sleep .05" hack).
--
--
You received this message from the
Santiago Alejandro Aguero wrote:
> While I was trying to write some vim code for testing a (async)
> functionality for Neomake plugin, I've noticed the following scenario:
>
>
> - Having the following shell script (with errors):
>
> #!/bin/sh
>
> a='$var'
>
> foo(
>
>
> - And the next vim
Daniel Hahler wrote:
> > Thanks, this is useful. Now we need to find out why we see an error or
> > nothing to read, while reading the pipe/socket should give us the
> > output. Adding some ch_logs() calls in channel_wait() could help
> > pinpoint it.
>
> Sorry, I have not patched/debugged
FWIW: this is the hack I've come up with for the Neomake tests:
https://github.com/neomake/neomake/pull/636/commits/6e767467b1680053c493a6fa8c656298e9f1b659
It wraps the command in "sh -c '…; sleep .1'".
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
> Thanks, this is useful. Now we need to find out why we see an error or
> nothing to read, while reading the pipe/socket should give us the
> output. Adding some ch_logs() calls in channel_wait() could help
> pinpoint it.
Sorry, I have not patched/debugged Vim, but want to add some findings
Santiago Agüero wrote:
> The script's output is being used as a way to check for any syntax error,
> it should print (and it is, in bash):
>
> /bin/sh errors.sh
> errors.sh: line 5: syntax error near unexpected token `newline'
> errors.sh: line 5: `foo('
>
> And yes, the job exits quickly, in
The script's output is being used as a way to check for any syntax error,
it should print (and it is, in bash):
/bin/sh errors.sh
errors.sh: line 5: syntax error near unexpected token `newline'
errors.sh: line 5: `foo('
And yes, the job exits quickly, in fact, if you use a short sleep (ie:
sleep
Santiago Alejandro Agüero wrote:
> While I was trying to write some vim code for testing a (async)
> functionality for Neomake plugin, I've noticed the following scenario:
>
>
> - Having the following shell script (with errors):
>
> #!/bin/sh
>
> a='$var'
>
> foo(
>
>
> - And the next vim
While I was trying to write some vim code for testing a (async) functionality
for Neomake plugin, I've noticed the following scenario:
- Having the following shell script (with errors):
#!/bin/sh
a='$var'
foo(
- And the next vim test code:
function! StartJob()
let g:job =
