public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Cc: Dmitry Katsubo <dma_k@mail.ru>
Subject: Re: Quotes around command-line argument that has unicode characters  are not removed
Date: Thu, 22 Mar 2018 17:25:00 -0000	[thread overview]
Message-ID: <a2f8e7e7dc6da9d4a38e3ea24269b185@mail.kylheku.com> (raw)
In-Reply-To: <1547310513.20180322142446@yandex.ru>

On 2018-03-22 04:24, Andrey Repin wrote:
> Greetings, Dmitry Katsubo!
> 
>> Dear Cygwin community,
> 
>> I observe the following on my Cygwin:
> 
> This is not cygwin, this is bare Windows.

That may be so, yet there may be an issue here for someone packaging
Cygwin programs for use as native Windows applications.

That is to say, there could potentially be something here that the 
Cygnal
project could address:

http://www.kylheku.com/cygnal/

Cygnal is an ultra-light fork of the Cygwin DLL that is intended for 
users like Dmitry Katsubo, who run Cygwin programs out of the Windows 
environment directly, after building them in Cygwin.

> 
>> when I put quotes around file that has
>> non-ASCII symbols, these quotes are passed to argv of the process 
>> literally,
>> otherwise they are removed. I would expect that there is a 
>> consistency.
> 
> Parameter unquoting done by the shell.
> CMD does that differently from POSIX shells.

As I seem to recall, CMD doesn't do anything, period! It passes the 
command line
as one big string. It has to since that's the OS mechanism.

The quoting conventions come from how various run-time libraries deal 
with that
string. An influential convention is that of the MS Visual C run-time 
library;
it behooves other run-times to be compatible with that for consistency 
with
programs whose main() was compiled with MSVC.


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

  reply	other threads:[~2018-03-22 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  5:41 Dmitry Katsubo via cygwin
2018-03-22 12:24 ` Andrey Repin
2018-03-22 17:25   ` Kaz Kylheku [this message]
2018-03-22 22:46     ` Dmitry Katsubo via cygwin
2018-03-25  0:04       ` Kaz Kylheku
2018-03-22 21:14   ` Dmitry Katsubo via cygwin
2018-03-23  7:58   ` Thomas Wolff
2018-03-23 12:20     ` Steven Penny
2018-03-22 13:35 ` Mikhail Usenko via cygwin
2018-03-22 15:35   ` Andrey Repin
2018-03-22 22:21     ` Dmitry Katsubo via cygwin
2018-03-27 10:05       ` Andrey Repin
2018-03-27 17:39         ` 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=a2f8e7e7dc6da9d4a38e3ea24269b185@mail.kylheku.com \
    --to=920-082-4242@kylheku.com \
    --cc=cygwin@cygwin.com \
    --cc=dma_k@mail.ru \
    /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).