Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows style path is not treated as a valid command. #273

Open
mashizora opened this issue May 23, 2024 · 0 comments
Open

Windows style path is not treated as a valid command. #273

mashizora opened this issue May 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@mashizora
Copy link
Contributor

In 0.40.0+, command not found error throws when calling an Windows executable file by Windows style path (separator is \\).

0.39.2 does not have this issue, It looks like an issue in deno-which implementation.

Reproduction

import { $ } from "jsr:@david/[email protected]";

await $`c:\\Windows\\explorer.exe`; // error

Output

dax: c:\Windows\explorer.exe: command not found
error: Uncaught (in promise) Error: Exited with code: 127
            throw new Error(`Exited with code: ${code}`);
                  ^
    at CommandChild.pipedStdoutBuffer (https://jsr.io/@david/dax/0.41.0/src/command.ts:785:19)
    at eventLoopTick (ext:core/01_core.js:168:7)
@dsherret dsherret added the bug Something isn't working label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants