Fix #45; quote set command to allow special chars in paths

[the-can-of-soup]

Summary

Paths containing certain special characters cause unexpected behavior. Fixed by quoting the SET command.

References

Fixes #45
Reopens #53

[ashrafiucse]

Hey — I hit the same bug last week (through a Playwright issue where someone had & in their folder name) and made the exact same change before I noticed this PR was already here.

I went ahead and opened #189 with the fix as well. The difference is I added a windows-only test that actually executes a shim from a dir & name path — everything else in the suite just snapshots the generated files, so nothing would've caught this class of regression.

One gotcha worth knowing if you'd rather keep pushing yours: the snapshot that actually needs regenerating is tap-snapshots/test/basic.js.test.cjs, not tap-snapshots/test-basic.js-TAP.test.js. That second file looks live but it's leftover from an older tap version, so as-is CI would still compare against the unquoted SET dp0=%~dp0 in the real snapshot and fail. npx tap --snapshot regenerates it.

Happy with either one getting merged, just want this to finally land after 6 years 🙂

[the-can-of-soup]

Oh, no problem at all! To be honest I just searched for the code and quoted the SET command as a quick-fix, and found #53 had done this before so just copied its changes. Glad to see someone make a more proper fix. 👍