From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Unexpected output from curl and wttr.in
Date: Sun, 22 Dec 2019 12:51:00 -0000 [thread overview]
Message-ID: <8aa102fd-f04d-6ec8-a6a1-a5694c0403e9@gmail.com> (raw)
In-Reply-To: <2f1ede36-c811-eb70-fde3-f0a4e7c70ffe@SystematicSw.ab.ca>
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
--
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
next prev parent reply other threads:[~2019-12-22 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:36 Mike MacEachern
2019-12-19 19:48 ` Marco Atzeri
2019-12-20 18:20 ` Csaba Raduly
2019-12-21 1:21 ` Marco Atzeri
2019-12-21 2:13 ` Mike MacEachern
2019-12-21 3:04 ` Marco Atzeri
2019-12-22 12:35 ` Brian Inglis
2019-12-22 12:51 ` Marco Atzeri [this message]
2019-12-24 9:20 ` Mike MacEachern
2019-12-25 22:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8aa102fd-f04d-6ec8-a6a1-a5694c0403e9@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).