public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: [BUG core?] Regression with parsing Windows’ command-line
Date: Sat, 3 Dec 2022 19:28:10 +0900	[thread overview]
Message-ID: <20221203192810.03c73015303ef3ad4fe241f3@nifty.ne.jp> (raw)
In-Reply-To: <20221203034030.a6ghnwcze4rkqeap@math.berkeley.edu>

On Fri, 2 Dec 2022 19:40:30 -0800
Ilya Zakharevich wrote:
> On Wed, Nov 16, 2022 at 04:48:25AM -0800, I wrote:
> > De-quoting (converting the Windows’ command-line into argc/argv) does
> > not remove double quotes if characters not fit for 8-bit (?) are present.
> > 
> > 	Broken in: CYGWIN_NT-6.1     Bu 3.3.4(0.341/5/3) 2022-01-31 19:35 x86_64 Cygwin
> > 	Works  in: CYGWIN_NT-6.1-WOW Bu 2.2.1(0.289/5/3) 2015-08-20 11:40 i686   Cygwin
> > 
> > To reproduce, do in CMD’s command line:
> > 
> >   D:\> D:\Programs\cygwin2022\bin\perl -wle "print for @ARGV" . "/i/" "/и/" .
> >   .
> >   /i/
> >   "/и/"
> >   .
> 
> I triple-checked
>   • with a Win10 machine (and a version of cygwin given above),
>   • with a fresh latest(=test)-cygwin-dll installation on a Win7 (as above) machine. 
> 
> Same bug everywhere.

This certainly seems to be a problem of cygwin1.dll.

Though I am not sure this is the right thing, I have confirmed
that the following patch solves the issue.

diff --git a/newlib/libc/locale/lctype.c b/newlib/libc/locale/lctype.c
index 644669765..732d132e1 100644
--- a/newlib/libc/locale/lctype.c
+++ b/newlib/libc/locale/lctype.c
@@ -25,11 +25,20 @@
 
 #define LCCTYPE_SIZE (sizeof(struct lc_ctype_T) / sizeof(char *))
 
+#ifdef __CYGWIN__
+static char	numsix[] = { '\6', '\0'};
+#else
 static char	numone[] = { '\1', '\0'};
+#endif
 
 const struct lc_ctype_T _C_ctype_locale = {
+#ifdef __CYGWIN__
+	"UTF-8",			/* codeset */
+	numsix				/* mb_cur_max */
+#else
 	"ASCII",			/* codeset */
 	numone				/* mb_cur_max */
+#endif
 #ifdef __HAVE_LOCALE_INFO_EXTENDED__
 	,
 	{ "0", "1", "2", "3", "4",	/* outdigits */


-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-12-03 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 12:48 Ilya Zakharevich
2022-12-03  3:40 ` Ilya Zakharevich
2022-12-03 10:28   ` Takashi Yano [this message]
2022-12-03 13:42     ` Takashi Yano
2022-12-03 15:29       ` Corinna Vinschen
2022-12-03 15:24     ` Corinna Vinschen
2022-12-03 15:39       ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2022-11-15  5:58 Ilya Zakharevich

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=20221203192810.03c73015303ef3ad4fe241f3@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=nospam-abuse@ilyaz.org \
    /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).