On 2018-03-22 18:10, Kaz Kylheku wrote:
> 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.co
On 2018-03-22 14:25, Andrey Repin wrote:
> Greetings, Mikhail Usenko!
>
>> In bare cmd.exe native-msvcrt binary is working OK with quoted non-ascii
>> arguments, while cygwin-flavor binary is not. But I don't know exactly which
>> level here: cmd.exe or msvcrt.dll/cygwin1.dll is responsible for
>>
On 2018-03-22 12:24, Andrey Repin wrote:
>
> This is not cygwin, this is bare Windows.
This is executable linked against cygwin1.dll. I personally call such
binaries "Cygwin programs". However it is run from Windows.
> Parameter unquoting done by the shell.
> CMD does that differently from POSIX
Dear Cygwin community,
I observe the following on my 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.
I have written a small C program that displays a
4 matches
Mail list logo
