The curl alias in powershell is not compatible so it is an inconvenience. Must be one of the worst decisions to make it into windows, which is saying a lot.

▲

NekkoDroid 6 days ago | parent | next [-]

The worst part is that Windows does ship cURL as a binary at `C:\Windows\System32\curl.exe` (may be dependent on some optional feature, dunno). Nowadays it does invoke this for me on my system, but I don't remember if I did something for this to be the case.

▲

al_borland 6 days ago | parent | prev [-]

Most of the aliases are for convenience when working in an interactive shell, which will generally be dealing with more basic functions of a command. For scripting it is best practice to use the full commandlet names.

▲

pletnes 6 days ago | parent [-]

Browsers let me copy-paste curl commands from developer tools. These don’t work with windows «curl».

I know a few flags of curl too. These also don’t generally work with «curl».

▲

naikrovek 6 days ago | parent [-]

So type “curl.exe” instead of “curl” or remove the alias in PowerShell.

	▲	pletnes 5 days ago \| parent [-]
		I just avoid windows whenever I can.