From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments
Date: Fri, 2 Oct 2020 20:22:04 -0600 [thread overview]
Message-ID: <CAJ1FpuNi1H5tXVVbhGm-0m+OcgmDkEYJ=48biPYmXEZ9saSP1Q@mail.gmail.com> (raw)
In-Reply-To: <CAFC9CLCtfMORMxAK6==jdwY5ZbX6jWwo+JCfDwM3njgvGduf0w@mail.gmail.com>
On Fri, 2 Oct 2020 at 15:41, Jérôme Froissart <> wrote:
>
> By discussing a merge request on another project [1], I think
> billziss-gh found a weirdness in the way Cygwin parses the command
> line arguments when non-ASCII characters come into play.
>
> EXPECTED BEHAVIOUR:
> cygwin should parse the following command line
> binary.exe --non-ascii "charaçtérs" --ascii "nothing-fancy-here"
Please show us the output from "uname -a" and "locale" run from the bash prompt.
Tell is more about "binary.exe". Is it compiled for cygwon with gcc,
for windows with mingw64 or windows with a native tool chain. Also are
you running it from a bash prompt or a cmd.exe prompt?
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
next prev parent reply other threads:[~2020-10-03 2:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 21:40 Jérôme Froissart
2020-10-03 2:22 ` Doug Henderson [this message]
2020-10-04 11:18 ` Andrey Repin
2020-10-06 21:36 ` Jérôme Froissart
2020-10-07 1:10 ` Andrey Repin
2020-10-07 22:21 ` Jérôme Froissart
2020-10-11 18:55 ` Andrey Repin
2020-10-07 2:20 ` Brian Inglis
2020-10-07 5:17 ` Thomas Wolff
2020-10-07 23:32 ` Brian Inglis
2020-10-08 0:59 ` Eliot Moss
2020-10-08 6:22 ` Brian Inglis
2020-10-13 16:30 ` Kaz Kylheku (Cygwin)
2020-10-14 21:47 ` Jérôme Froissart
2020-10-14 22:14 ` Jérôme Froissart
2020-10-15 5:14 ` UTF-8 quoted args passed to program include quotes when run from cmd Brian Inglis
2020-10-19 2:32 ` Unconsistent command-line parsing in case of UTF-8 quoted arguments Kaz Kylheku (Cygwin)
2020-10-13 17:34 ` Brian Inglis
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='CAJ1FpuNi1H5tXVVbhGm-0m+OcgmDkEYJ=48biPYmXEZ9saSP1Q@mail.gmail.com' \
--to=djndnbvg@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).