Earlier quoted context omitted.
No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?
Maybe it's just me, but I find PowerShell to be so verbose. Why does every parameter have to have consist of a camelcased sentence? I'm a good typist, but I don't think what you wrote is better than curl wttr.in But that might just be (my) programming.
Curl Wttr.in
31–40 of 128 posts
Re: Curl Wttr.in
#32A good opportunity to remind everyone that we finally inboxed curl into Windows 10, so this works (with color output) from a stock Windows command prompt. Better late than never, I hope.
Glad to hear that, though I wasn't aware color output now works on windows command. I was under the impression the ansi.sys driver or similar was still necessary for color support.
The console subsystem is open-source at https://github.com/microsoft/terminal. Feel free to file bugs, complain, or what have you. That’s what we’re here for!
To quote GP, “better late than never, I hope”.
Re: Curl Wttr.in
#33Re: Curl Wttr.in
#34Earlier quoted context omitted.
Isn't Windows 10 free?
there are ebay keys for a couple dollars
Re: Curl Wttr.in
#35 curl wttr.in/Moon
Shows current lunar phase.I use Termux[0] on my phone with curl installed. Pretty handy.
Also, check out rate.sx[1] from the same author:
curl rate.sx
Shows information about current exchange rates of cryptocoins.More similar console services: https://github.com/chubin/awesome-console-services
[0]: https://termux.com/
Re: Curl Wttr.in
#36Earlier quoted context omitted.
No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?
Serious question -- not a flame war :) I honestly can't tell if this is sarcastic or not. I've been typing `curl -O http: ...` into command prompts for decades, and that Powershell incantation looks awfully unwieldy. In what way is it the happy path?
Re: Curl Wttr.in
#37Re: Curl Wttr.in
#38Earlier quoted context omitted.
No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?
Maybe it's just me, but I find PowerShell to be so verbose. Why does every parameter have to have consist of a camelcased sentence? I'm a good typist, but I don't think what you wrote is better than curl wttr.in But that might just be (my) programming.
irm wttr.in
irm is an alias for Invoke-RestMethod which is similar to Invoke-WebRequest but better for non-html responses like json or plain text.Re: Curl Wttr.in
#39A good opportunity to remind everyone that we finally inboxed curl into Windows 10, so this works (with color output) from a stock Windows command prompt. Better late than never, I hope.
Can you explain more about why you thought this was a good opportunity to interject an advertisement for your product?
Re: Curl Wttr.in
#40It turns out my terminal was set at 125 characters wide and wttr.in outputs a 125 character width display.