Unexpected output from curl and wttr.in

[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, Dec 19, 2019 at 3:10 PM Mike MacEachern wrote:
>>
>> Useful path search diagnostic commands:
>>
>> $ which -a curl
>> alias curl='curl -sSL'
>> Â Â Â Â Â Â Â Â  /usr/bin/curl
>> Â Â Â Â Â Â Â Â  /proc/cygdrive/c/.../cygwin32/bin/curl
>> Â Â Â Â Â Â Â Â  /proc/cygdrive/c/WINDOWS/System32/curl
>> $ man -awW curl        # -W also shows .../man/cat#/ pages
>> /usr/man/man1/curl.1.gz
>> /proc/cygdrive/c/.../cygwin32/usr/share/man/man1/curl.1.gz
>> $ whereis curl
>> curl: /usr/bin/curl.exe /usr/include/curl
>> /proc/cygdrive/c/.../cygwin32/bin/curl.exe
>> /proc/cygdrive/c/WINDOWS/System32/curl.exe /usr/share/man/man1/curl.1.gz
>>
> 
> sure Mike,
> but none of these will work if you are biased
> to think that other problems are around
> 
> https://cygwin.com/acronyms/#PEBCAK
> 
> is the biggest ostacle to any debugging
> 
> Regards
> Marco
> 
> 
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.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple