Nate Fischer

If the goal is to have an async-exec which returns a promise, how about we add support for: ```js shell.exec('cmd', { async: 'promise' }); ``` --- > global config that...

`execa` seems to be fine to give a Promise-y replacement for `shell.exec()`, although it of course does nothing for non-exec commands (which is what this issue is tracking).

@chase-moskal proposal is reasonable. I guess I'd like to find a way to share implementation where possible, but it's not obvious how to do that. I'll gladly review PRs for...

Looks like a bug. I can repro on my Linux system as well. Let me know if you're interested in sending a fix.

Looks like a bad interaction with passing directories as arguments. ```sh shx cp -RLu srcDir/baz.txt targDir/srcDir/baz.txt # No bug shx cp -RLu srcDir targDir # This has the bug ```...

I'm still hoping to work on this. Unfortunately, it's really hard to provide reasonable behavior on Windows (#866 basically works for unix). I vaguely remember issues with v4/v5--now that we've...

No major update. This is quite difficult to get right for Windows, and I don't have a machine anymore to speed up investigation. This is something I'm very interested in...

Updated the description, but this is not a security vulnerability/fix, rather this is an implementation of a feature request. Please follow #945 if you'd like to read discussion regarding how...

I worked around those issues in #866 by using https://github.com/sindresorhus/execa, which seems to handle Windows much more nicely than anything I had figured out by hand. That PR implemented "step...

@AlfredssonErik could you try cloning the repo and verifying PR #975? I don't have a Windows machine handy.