Make use of the message loop to implement non-blocking versions of IO functions #2
Description
Here's a few that come to mind:
- childStart(command, args, stdoutcb[, stderrcb]) : spawns a child process, accepts one or two function names as extra arguments, these functions will be called for chunks of data in stdout/stderr. The function should return a handle that can be used to kill the child process or feed data to stdin through other helper functions: childStop/childSend(for example)
- globStart(): same as 'glob()' but accepts a function name that will be called for chunks of filenames discovered. the function should return a handle that can be used to stop globbing through another funciton, globStop() for example.
Many plugins such as syntastic could make use of 'childStart' to talk to other processes more efficiently.
ctrlp could make use of globStart when searching big file trees.