Nate Fischer

Yeah, I can repro. Seems like a bug in `grep()` rather than `ls()`. ```sh shx ls | shx grep -v 'foo' # bug shx ls | grep -v 'foo' #...

Just to clarify, `npm_package_mkdirs` is an environmental variable? --- #65 mentions the cross-env package too. This sounds like a reasonable feature for shx (shelljs already exposes this under `shell.env.NAME_OF_VAR`). In...

Oh, I see. I wasn't familiar that npm package attributes were set as environmental variables. Thanks for explaining. Another thing we have to worry about: `$npm_package_mkdirs` could contain spaces, and...

> As for spaces in the dir names, couldn't the programmer simply quote them like this: export foo='1 "2 3"' which produces: echo $foo => 1 "2 3" Try this:...

> My current solution uses cross-env-shell, in the second post above. I wonder how they handle it? We could check their code. They're accepting a full command string. So `process.argv`...

Yeah, unfortunately it seems like there's no obvious way to support env variables without running into these edge cases. It's a good feature request, and it would've been really nice...

> Can we not start with this very simple support and work our way up to more complex edge cases as we go? The issue is that supporting that case...

@goerwin we don't support executing arbitrary commands at the moment, so I don't think there's any benefit to defining variables in-line (although I can see the benefit of combining these...

I don't think this is currently possible in shx. We support `shx true` and `shx false` (and the OS will support `&&` and `||`), but I believe these are not...

It looks like folks on the Chromium build team are already thinking about this! :smile: I suggest you click the "star" icon for https://crbug.com/1163978 if you would like to be...