I get "Weather report: not found" on the first line and then a 3 day forecast for idk what location.
try `curl wttr.in/Munich` (with your location specified instead of Munich)
`curl wttr.in`: Weather in your terminal
101–110 of 147 posts
Re: `curl wttr.in`: Weather in your terminal
#102Earlier quoted context omitted.
The terminal (or rather terminal emulation) is a mistake, people should stop glorifying it. It has no inherent value, beyond being able to run historical software that was bound to a terminal. Most of all one should stop confusing the terminal and the shell, which remains an interesting concept.
Then where should the shell be run?
Re: `curl wttr.in`: Weather in your terminal
#103Earlier quoted context omitted.
The terminal (or rather terminal emulation) is a mistake, people should stop glorifying it. It has no inherent value, beyond being able to run historical software that was bound to a terminal. Most of all one should stop confusing the terminal and the shell, which remains an interesting concept.
I have no idea what that comment means.
Re: `curl wttr.in`: Weather in your terminal
#104Earlier quoted context omitted.
The terminal (or rather terminal emulation) is a mistake, people should stop glorifying it. It has no inherent value, beyond being able to run historical software that was bound to a terminal. Most of all one should stop confusing the terminal and the shell, which remains an interesting concept.
Hard disagree, it has a lot of value and there's a reason it still exists and lots of tooling is still developed for running in terminals and shells, sometimes as exclusive target. Problems with untrusted, unknown input from any source affects *all* software that process it, internet browsers, document editors, archive extractors, even just opening a file can do lots of funky stuff depending on the file system.
Re: `curl wttr.in`: Weather in your terminal
#105Re: `curl wttr.in`: Weather in your terminal
#106Re: `curl wttr.in`: Weather in your terminal
#107Earlier quoted context omitted.
I'm speechless. I never expected running curl could lead to such a security disaster.
`sudo curl | sh` to deploy my awesome service that definitely isn't a bitcoin miner, promise.
In one command you pipe the output to `sh` which will run whatever instruction it receives. In another command you just ask for an output from `curl`, doing so should not cause any side effect than the output action itself.
Re: `curl wttr.in`: Weather in your terminal
#108Re: `curl wttr.in`: Weather in your terminal
#109Earlier quoted context omitted.
try `curl wttr.in/Munich` (with your location specified instead of Munich)
Thanks. The odd thing is that the weather report looks somewhat accurate. I'm not behind any proxy. Let me know if I can help debug.
Re: `curl wttr.in`: Weather in your terminal
#110Earlier quoted context omitted.
Begging the question isn't usually used like this these days, even if it did originate thus. The English language is used the way English speakers use it; yes, even that is quite circular, because there is no formal academy setting down rules that everyone agrees on. Institutions only teach stylistic choices. We use beg the question in exactly the way you say we shouldn't far more often than not to the point that its…
I'm well aware. In this case, I tend to strongly prefer the prescriptivist view to the prescriptivist, and misuse generates confusion rather than clarity. Words ... should mean things. Particularly when they're specifically referring to illegitimate reasoning in the first place. "Enormity", "disinterested", and "very unique" are others on my list.