If you're on Windows, run this once:

  'Remove-Alias curl, wget' >> $PROFILE

Now please stop whining about these stupid aliases.

▲ petterroea 6 days ago | parent [-]

This feels like a very dishonest take because the problem being discussed is clearly beginners being confused. How does your solution scale to the problem at hand?

▲

fainpul 6 days ago | parent [-]

Of course it doesn't help if a beginner doesn't understand why their curl command fails. I wrote this half in jest, because everytime PowerShell comes up, people like to Bash it for its stupid aliases on Windows. Yes these aliases are really stupid, but if you are using PS on Linux, it's not an issue and if you are on Windows, you just remove those aliases and continue living your life.

Some examples from this discussion:

> The curl alias in powershell is not compatible so it is an inconvenience.

> *nix fanboys were totes fine with wget and ls being an aliases in PowerShell for years but when they found out what PS is coming to Linux they made a biggest stink.

> Only the old powershell.exe builtin to Windows has these aliases and it’s worse today because curl.exe is builtin and the curl alias takes priority when you run just curl.

> It's wget for Windows all over again

> Ah yes, the 'curl' alias in powershell, vs the 'curl.exe' binary that uses the traditional options.

	▲	tracker1 6 days ago \| parent [-]
		And thus, I mostly use git's msys bash in my work Windows machine(s).