Re: Unexpected output from curl and wttr.in

2019-12-25 Thread Andrey Repin
Greetings, Mike MacEachern! > Huh? I thought we solved this just by installing the Cygwin native > version of curl. Nothing else required, by simply installing Cygwin's > own curl, the Windows version is automatically not used by default, > therefore no other work was required. which -a curl

Re: Unexpected output from curl and wttr.in

2019-12-23 Thread Mike MacEachern
On 12/22/2019 6:21 AM, Marco Atzeri wrote: > Am 22.12.2019 um 07:00 schrieb Brian Inglis: >> On 2019-12-20 19:13, Marco Atzeri wrote: >>> Am 20.12.2019 um 23:42 schrieb Mike MacEachern: On 12/20/2019 2:36 PM, Marco Atzeri wrote: > Am 20.12.2019 um 17:29 schrieb Csaba Raduly: >> On Thu,

Re: Unexpected output from curl and wttr.in

2019-12-22 Thread Marco Atzeri
Am 22.12.2019 um 07:00 schrieb Brian Inglis: On 2019-12-20 19:13, Marco Atzeri wrote: Am 20.12.2019 um 23:42 schrieb Mike MacEachern: On 12/20/2019 2:36 PM, Marco Atzeri wrote: Am 20.12.2019 um 17:29 schrieb Csaba Raduly: On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote: Useful path se

Re: Unexpected output from curl and wttr.in

2019-12-21 Thread Brian Inglis
On 2019-12-20 19:13, Marco Atzeri wrote: > Am 20.12.2019 um 23:42 schrieb Mike MacEachern: >> On 12/20/2019 2:36 PM, Marco Atzeri wrote: >>> Am 20.12.2019 um 17:29 schrieb Csaba Raduly: On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote: >>> Thanks for checking >>> not noted the first time:

Re: Unexpected output from curl and wttr.in

2019-12-20 Thread Marco Atzeri
Am 20.12.2019 um 23:42 schrieb Mike MacEachern: On 12/20/2019 2:36 PM, Marco Atzeri wrote: Am 20.12.2019 um 17:29 schrieb Csaba Raduly: On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote: Thanks for checking not noted the first time: it works on my 64bit but fails on 32bit and the r

Re: Unexpected output from curl and wttr.in

2019-12-20 Thread Mike MacEachern
On 12/20/2019 2:36 PM, Marco Atzeri wrote: > Am 20.12.2019 um 17:29 schrieb Csaba Raduly: >> On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern >> >> wrote: >> >>> I'm currently at a loss with how curl is parsing wttr.in.  Now I've used >>> it without in the past, but it seems right now it's really s

Re: Unexpected output from curl and wttr.in

2019-12-20 Thread Marco Atzeri
Am 20.12.2019 um 17:29 schrieb Csaba Raduly: On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote: I'm currently at a loss with how curl is parsing wttr.in. Now I've used it without in the past, but it seems right now it's really struggling. I've checked and echo $LANG reports en_US.UTF-8 ju

Re: Unexpected output from curl and wttr.in

2019-12-20 Thread Csaba Raduly
On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote: > I'm currently at a loss with how curl is parsing wttr.in. Now I've used > it without in the past, but it seems right now it's really struggling. > I've checked and echo $LANG reports en_US.UTF-8 just in case that was > the issue but it's n

Re: Unexpected output from curl and wttr.in

2019-12-19 Thread Marco Atzeri
Am 19.12.2019 um 15:06 schrieb Mike MacEachern: I'm currently at a loss with how curl is parsing wttr.in. Now I've used it without in the past, but it seems right now it's really struggling. I've checked and echo $LANG reports en_US.UTF-8 just in case that was the issue but it's not. Now I've t

Unexpected output from curl and wttr.in

2019-12-19 Thread Mike MacEachern
I'm currently at a loss with how curl is parsing wttr.in. Now I've used it without in the past, but it seems right now it's really struggling. I've checked and echo $LANG reports en_US.UTF-8 just in case that was the issue but it's not. Now I've tried both mintty and the Windows console (and chan