Andrew Stewart wrote:
> On Sunday, 7 February 2016 15:18:38 UTC, Bram Moolenaar wrote:
> >
> > Now that the basic channel and job support is there, I would like to
> > invite plugin writers to give feedback. We probably need some more
> > features and/or change how things work.
>
> Is it possible to read the job's stdout once it has finished?
>
> I'm thinking of vim-gitgutter which runs git-diff, parses the diff and
> updates signs. How would I read the resulting diff if I ran it in a
> vim job?
Yes, you will be able to start the job with only an exit handler, and
when that handler is called do a ch_readall() on stdout. Something like
that. I didn't have this in the spec, but we do actually already have
it implemented internally, a non-blocking read on the channel.
--
hundred-and-one symptoms of being an internet addict:
224. You set up your own Web page. You set up a Web page for each
of your kids... and your pets.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
