Simon Marchi

Ok, thanks for the detailed answer. Knowing nothing about the ccache code base, I would think that you could keep those separate lists, but with each argument keep what its...

Hi @jamores, The file you modified is maintained in the [autoconf archive](https://github.com/autoconf-archive/autoconf-archive), and we merely copy it in our repository. Please send a patch to them, they will help you...

Hmm not really. It's not related to the process exit. It is that we want to be able to know whether the process was started successfully (meaning, the exec system...

We have already tried to get the approval for another Microsoft project (language-server stuff). IIUC, the problem our legal department has with the Microsoft CLA is that it applies to...

> @simark You trigger the success event on `nextTick`, but it is not guaranteed that the exec call already happened in the forked process (the kernel process scheduler could have...

Here's where it's done in libuv: https://github.com/nodejs/node/blob/3fe9267592cfef01b50f4f94eaa50b2dc495eb1a/deps/uv/src/unix/process.c#L462

Even better, it should be fixed. @marcdumais-work, is the situation still the same at Ericsson (still not allowed to contribute to this project)?

I don't really understand what is the expected typical scenario. I have set GOPATH in my .bashrc to point to `~/gopath`, so that when I type `go get ...` to...

> That's how I read the recommendation on the Go-lang page. I cannot imagine that to be practical either. With one GOPATH per project that's what npm does: copy every...

Hmm the MI should really not be on the same channel as the program output.