Alexej Yaroshevich

Same trouble here. Help please. What to do with it?

Am I right that we should close this? Issue is pretty confusing in opened state. Related: https://github.com/mhevery/jasmine-node/issues/366

Is it really possible to catch this kind of errors? Except domains usage.

@arikon Can you please fill up this proposal?

@Yeti-or I've tried to run this code: ```js const coa = require('coa'); coa.Cmd() .name('ololo') .opt('opt').short('o').long('opt').name('opt').title('opt').end() .act((opts, args) => { console.log(opts, args); }) .run(process.argv.slice(2)); ``` with `node this-code.js --opt='--subopt --subopt'` and...

@veged Don't merge please. Need to discuss. Here I have 2 questions. Why not to split this into independent package? But if split how to pretty inject this into the...

@veged Okay. I'll wait for review then ;-)

@veged I'm stuck on stream while reworking tests that using spawn. Can we drop 0.8 support and use Streams v2? It's available since v0.10.

@veged well. nvm. I'll do it with classic streams.

It's a bug, dude ;-(