Using jobs to write an async building system, I can not find a callback which I 
can relay on it to clean my build state (unlet job object and output 'finished' 
to quickfix window):

Sometimes 'close_cb' is invoked after 'exit_cb' and sometimes 'exit_cb' is 
invoked after close_cb and even 'callback'will happen **after** 'exit_cb' and I 
always get something in quickfix window like:

hello.c:1: xxxxxxx       -> 'callback'
hello.c:2: xxxxxxx       -> 'callback'
hello.c:3: xxxxxxx       -> 'callback'
[Finished in 2 seconds]  -> 'exit_cb'
hello.c:4: xxxxxxx       -> 'callback'
hello.c:5: xxxxxxx       -> 'callback'
(pipe close)             -> 'close_cb'

and sometimes it become this:

hello.c:1: xxxxxxx       -> 'callback'
hello.c:2: xxxxxxx       -> 'callback'
hello.c:3: xxxxxxx       -> 'callback'
hello.c:4: xxxxxxx       -> 'callback'
hello.c:5: xxxxxxx       -> 'callback'
(pipe close)             -> 'close_cb'
[Finished in 2 seconds]  -> 'exit_cb'

I just can't figure out which callback is the last one ? and when should I 
dispose my job state ? 'exit_cb' or 'close_cb' ?

Is this possible to guarantee that 'exit_cb' will always be called at last 
(after 'close_cb' and any other 'callback' / 'out_cb' / 'err_cb') ?

If so, my building system will be much easier.

-- 
-- 
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.

Raspunde prin e-mail lui