public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: Unexpected output from curl and wttr.in
Date: Fri, 20 Dec 2019 18:20:00 -0000	[thread overview]
Message-ID: <CAEhDDbCM5Ohe6KXKVjw+emmsaCQ761xQMfFieySag2uoZuPv+w@mail.gmail.com> (raw)
In-Reply-To: <qtg04k$67in$1@blaine.gmane.org>

On Thu, Dec 19, 2019 at 3:10 PM Mike MacEachern <maceach.m@h-networks.net>
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 not.  Now I've tried both mintty and the Windows
> console (and changed ForceV2 to 0 as well), no dice.
>
> What's interesting though if I use Cygwin to SSH into my Linux running
> laptop, curl's output looks fine, so the issue doesn't appear to be
> terminal related, unless there's something else I'm missing.  Here's a
> screenshot of what's going on.
>
> https://i.imgur.com/NNgtmlD.png
>
>
Works just fine for me on Windows 10 and mintty
https://imgur.com/ugWl9BY

Csaba

-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant
way
to get the wrong information: this is what you want. - Scott Meyers
(C++TDaWYK)

--
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

  parent reply	other threads:[~2019-12-20 16:29 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 [this message]
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
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=CAEhDDbCM5Ohe6KXKVjw+emmsaCQ761xQMfFieySag2uoZuPv+w@mail.gmail.com \
    --to=rcsaba@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).