Add workaround for pushd and popd to README #122
Conversation
Codecov Report
@@ Coverage Diff @@
## master #122 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 3 3
Lines 22 22
=====================================
Hits 22 22Continue to review full report at Codecov.
|
| @@ -85,8 +85,8 @@ Due to the differences in execution environments between ShellJS and `shx` (JS v | |||
| | Unsupported command | Recommend workaround | | |||
| | ------------------- | -------------------- | | |||
| | `shx cd` | Just use plain old `cd` (it's the same on windows too) | | |||
| | `shx pushd` | No workaround | | |||
| | `shx popd` | No workaround | | |||
| | `shx pushd` | Just use plain old `pushd`. Use forward slashes and double-quote the path. (e.g. `pushd "../docs"`. This would fail on Windows without the quotes) | | |||
There was a problem hiding this comment.
Can you point me to a source explaining why this fails? As I recall (memory is a bit hazy) cmd.exe generally respects forward slashes as path separators. I don't remember quotes really being needed for this.
There was a problem hiding this comment.
Most cmd commands and all cmd examples expect backward slashes (like all of Windows). Some commands however support forward slashes, and so do the lower level win32 API functions. Other cmd commands, however, choke on forward slashes and I don't know why. The only explanation I have is this:
There was a problem hiding this comment.
Huh, ok. Good enough for me, thanks for the screenshot.
As discussed in #121.