4 ms·
MUST is a strong word. I would rather not have pijul handling wildcards in Command Prompt. After all, who uses Command Prompt nowadays, when WSL2 and PowerShel
by sam_lowry_ 5y ago
MUST is a strong word. I would rather not have pijul handling wildcards in Command Prompt. After all, who uses Command Prompt nowadays, when WSL2 and PowerShell are available at the + button in Windows Terminal.
- alkonaut 5y agoIt’s a must if you consider the windows platform to only have the native windows shell(s). I have no data, but I’d wager cmd is still much more widely used than either ps or wsl is. Of course the dominance of windows on the desktop among developers is smaller than it is elsewhere, but it wouldn’t even surprise me if as many git users use cmd as any posix shell.
- WorldMaker 5y agoPowerShell doesn't expand wildcards by default either, because it also assumes that commands handle their own wildcards by default. You can cobble together the expansion somewhat easily yourself with something like Resolve-Path in PowerShell, but PowerShell doesn't use a posix-like approach here with "native" commands either because Windows (and DOS) has always left wildcard handling to EXEs by default.